Database changing records

[lburgess]

I have a database that I created in 2008 that has worked perfectly... now a new user has starting causing errors stating that the database forms are switching records without her changing them, what would be the cause of this and is there possible a report I could run everyday to see what changes were made?



I did notice it switch on me one time in 7 years but it seems to do it to her at least 7 or 8 times a day...

Any help would be greatly appreciated

[alansidman]

Is it possible that she is using the mouse to scroll between fields on the forms. I recall several years ago when working in Access 2002 and 2003 that you needed to tab between fields or move the mouse. When people used the scroll mouse because they were used to doing it in excel, we got lots of input errors. Don't know if this is an issue with later versions of Access or not.

[John_G]

One thing to check is the setting of the "Cycle" property of the forms. If it is set to "All records", then tabbing out of the last field in the form will go to the next record. To prevent that, set the property to "Current Record"

John

[June7]

There is no intrinsic functionality to report on changes in data. This would involve VBA and more tables for an audit log process. Review: http://allenbrowne.com/AppAudit.html

The two suggested causes are the most likely. However, without actually watching the user interact with form and witnessing the behavior, hard to be sure. The next time she feels the records have 'switched' inexplicably, have her describe the exact steps she exercised just before the apparent 'switch'.

[lburgess]

I thought this was the problem in the beginning but she swears she does not use the scroll.

The switch happens she says when she moves into the comments field.

[June7]

Can you replicate the behavior? What happens when you do the same thing on your computer? Does the switch actually happen when entering the control or when leaving? Does it happen every time?

[ssanfu]

Is this a stand alone dB? Or is the dB split?

If split, is the BE on a shared computer/server?
And each user has their own *copy* of the FE on their own computer?

[lburgess]

We use one copy on a shared server and multiple people are in at the same time

[June7]

Conventional wisdom says that will eventually cause corruption. I have one very simple database that is set up like that because that's what the users insisted on (was supposed to be a temporary solution while awaiting development of a more sophisticated program). That db has not one stitch of code - macro or VBA. It's been running well for couple years.

Ideally, a multi-user database should be split and each user has their own copy of the frontend.

[ssanfu]

Yup... disaster waiting to happen.

You do have backups.... Right???? At least Daily??? Hourly would be better... (IMO)