Re: Me.Dirty - Where to put this logic?

Tech-Archive recommends: Fix windows errors by optimizing your registry

It wouldn't surprise me if it is taking users a long time to fill out the
form. Not because the form is too long or complicated, it is because they
are doing health screenings of kids while they're entering the data. When we
first started to get the error, it was sporratic. Then when we shut down the
six computer and just worked on the application that is on the server we even
got the error. Since each kids goes to a different station, the record
dealing with that kid is only open at one time. I don't think there would be
any commonality between the users and the records they have pulled up.

I've tried including the timestamp that has been suggested in a lot of forums
and this change doesn't seem to resolve the write conflict error either. I
do not have any fields that are bit size. Is there anything else that I am
missing? I do have memo fields, but I really do not want to have to break
those down to seperate tables or change them to text fields. We get a lot of
school nurses who can be wordy and the memo field helps.

We've received the error when opening up a form (i've incorporated a search
feature that returns results in a list box - user can double click on the
record or select the open form button to open it up) and we've seen the error
when a user was trying to enter data. I'm stumped!

I've even seen forums where they say this is a known bug for Access and to
deal with it, however, I would really like to exhaust all outlets before
concluding that. Would the wireless connection play a part? Would it help
to be wired? I feel like I'm grasping for straws. :-)

Dirk Goldgar wrote:
Okay,

[quoted text clipped - 28 lines]
setup, I can set many places to put it, I just need to make sure it's
in the right spot so the error goes away. Please let me know.

When the focus changes from the main form to a subform, the main form's
record will be saved automatically if the form is dirty. When the focus
changes from a subform to the main form, the subform's record will be
saved automatically, if the subform is dirty. So there's no point in
trying to save records as you switch between main form and subform.

Is it taking the users a long time to fill out the form or subform, so
that the record remains dirty for a long time? You say that the users
are never "working on the same person at the same time." Given that you
have a SQL Server back-end, I'm not sure why you're getting write
conflicts, unless "working on a person" involves updating records that
may be in common between two "persons". That is, unless your problem
isn't really one of true write conflicts, but rather a configuration or
data problem that is causing Access to *think* there's a write conflict
when there really isn't. Do you get these conflict messages all the
time, or only occasionally? Do they really seem to correspond to
situations where users are updating the same records?


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200703/1

.

Quantcast