A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Using Forms
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

To Steve Schapel, another question?



 
 
Thread Tools Display Modes
  #1  
Old May 30th, 2004, 09:17 PM
Sandra
external usenet poster
 
Posts: n/a
Default To Steve Schapel, another question?

Thanks Steve, I see how to fix that problem. Now for
another related issue-
If the user hits the EDIT button, this sets the
AllowEdits YES, and turns the screen red. Now what I
have discovered is that unless you actually change
something in the record there is no update, therefore the
switch isn't reset again to NO by the proc in
AfterUpdate. So for instance if you hit the EDIT button,
then move to another record, you are still in the EDIT
mode. This also happens if you move to a different tab on
the form.
What I am trying to achieve is a method where each record
can only be edited one at a time, and only by a conscious
effort with the EDIT button, with fail safes if you move
from record to record. We are a charity and our office
staff and volunteers have very limited knowledge of
databases. I have had many problems maintaining the
integrity of the tables because they type into the wrong
fields or forget the procedures when using Find, and type
over the existing data.
Thanks so much for your help,
Sandra
  #2  
Old May 30th, 2004, 11:49 PM
Turner
external usenet poster
 
Posts: n/a
Default To Steve Schapel, another question?

You can reset the properties on the forms using the "On
Current" event. This event fires each time you move to a
new record. Check out "Order of Events" in the Help file.

Good Luck!

-----Original Message-----
Thanks Steve, I see how to fix that problem. Now for
another related issue-
If the user hits the EDIT button, this sets the
AllowEdits YES, and turns the screen red. Now what I
have discovered is that unless you actually change
something in the record there is no update, therefore

the
switch isn't reset again to NO by the proc in
AfterUpdate. So for instance if you hit the EDIT button,
then move to another record, you are still in the EDIT
mode. This also happens if you move to a different tab

on
the form.
What I am trying to achieve is a method where each

record
can only be edited one at a time, and only by a

conscious
effort with the EDIT button, with fail safes if you move
from record to record. We are a charity and our office
staff and volunteers have very limited knowledge of
databases. I have had many problems maintaining the
integrity of the tables because they type into the wrong
fields or forget the procedures when using Find, and

type
over the existing data.
Thanks so much for your help,
Sandra
.

  #3  
Old May 31st, 2004, 07:49 AM
Sandra
external usenet poster
 
Posts: n/a
Default To Steve Schapel, another question?

Thank you!
-----Original Message-----
You can reset the properties on the forms using the "On
Current" event. This event fires each time you move to

a
new record. Check out "Order of Events" in the Help

file.

Good Luck!

-----Original Message-----
Thanks Steve, I see how to fix that problem. Now for
another related issue-
If the user hits the EDIT button, this sets the
AllowEdits YES, and turns the screen red. Now what I
have discovered is that unless you actually change
something in the record there is no update, therefore

the
switch isn't reset again to NO by the proc in
AfterUpdate. So for instance if you hit the EDIT

button,
then move to another record, you are still in the EDIT
mode. This also happens if you move to a different tab

on
the form.
What I am trying to achieve is a method where each

record
can only be edited one at a time, and only by a

conscious
effort with the EDIT button, with fail safes if you

move
from record to record. We are a charity and our office
staff and volunteers have very limited knowledge of
databases. I have had many problems maintaining the
integrity of the tables because they type into the

wrong
fields or forget the procedures when using Find, and

type
over the existing data.
Thanks so much for your help,
Sandra
.

.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 10:08 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.