Mysterious, Magical, Menacing ERROR !!!!

  • Thread starter Thread starter jef
  • Start date Start date
J

jef

Yes...another "Data-Entry" question. I have a form that can be opened
in either add-mode or edit-mode. The form is for entering in work
orders. When people wish to search or change work orders they will
click on the button that opens the form in edit-mode. The "data entry"
option is changing to "yes" so they can't view any records. I switch
the option back to "no" and it will work fine for a couple of days the
switch back again.

I want to fix this thing once and for all!!! Any ideas?

p.s. - this database is on a shared drive and is only used by about
6-8 people. It's only purpose is to hold these work orders.
 
Yes...another "Data-Entry" question. I have a form that can be opened
in either add-mode or edit-mode. The form is for entering in work
orders. When people wish to search or change work orders they will
click on the button that opens the form in edit-mode. The "data entry"
option is changing to "yes" so they can't view any records. I switch
the option back to "no" and it will work fine for a couple of days the
switch back again.

I want to fix this thing once and for all!!! Any ideas?

p.s. - this database is on a shared drive and is only used by about
6-8 people. It's only purpose is to hold these work orders.
Click to expand...

One suggestion would be to leave Data Entry off; add a line in the
Form's Open Event VBA code

DoCmd.GoToRecord, , acLast


John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps
 
a couple things you might check: 1) if your db is Access 2000 or newer, go
to Tools|Options|General tab. if there is a checkmark next to Name
AutoCorrect, remove the checkmark. then close and compact the db. 2) is
there a "Close" button on the form? if so, you might want to change the
default Close action (which is "Prompt", in both a macro and in VBA) to
Save: No in a macro, or to

DoCmd.Close , , acSaveNo

in VBA. saving a form in the Close action does *not* save the record, it
saves the form object in its' current state. if your OpenForm action is
setting the DataEntry property to Yes or No, depending on which button the
user clicks, then saving the form on Close will make that setting permanent.

btw, it sounds like you have multiple users accessing a single frontend or
monolithic database on the shared drive. if more than one person is using
the database at the same time, it's prone to corruption problems -
especially if the code is changing a form property (on Open) and then saving
it (on Close). the recommended setup is a split db: backend (tables only)
on the server, and frontend (queries, form, etc) copy on each user's hard
drive.

hth
 
Back
Top