Records Changing by Themselves

[Guest]

I have a Sales Service database to track service and sales calls.
I've also got an Audit Log attached to track changes to records.

The other day, one of the records changed it's self from "Sales" to "Service".

It didn't show up on the Audit Log as if someone changed it, it was Sales
one day and then Service the next.

How can that happen? How can records change themselves? Is this whole
thing going to explode and everything go corrupt???

I am running it on a 2003 Access format and it is split.

Please help, I was worring about it so much that I didn't sleep much last
night!

 

[Guest]

Records DO NOT change themselves!

There is a reason for this, it is a question of understanding what is
causing this to happen. Sadly, there is no easy answer. You need to go
through your code to see if inadvertantly there is a piece of code performing
this action? Did someone edit/change/run a query that did this? Did a user
do this? Identify each object which refers to your table where the data is
changing and then review each object carefully. Do your users have mdb or
mde? Basically can they make changes to their front-end? (For security...you
should deploy the front-end as an mde to your users)

You need to start reviewing these 1 by 1 to identify the issue. Also, start
by doing a compact and repair of both your back and front ends.

 

[Guest]

That's pretty much what I said...the DON'T change themselves!
I'll try your suggestions.
Thanks!

 

[Carl Rapson]

It depends on how you are logging to the Audit Log. Obviously, there is some
way to update the table that bypasses your normal procedure. If this is done
from a form, in what event are you logging? Is there a way for the user to
bypass that event somehow? For example, if you have a command button to
close the form and that's where your audit code is, is there a way to close
the form without the command button? Another situation I have run into
involves the mouse scroll wheel. Sometimes forms have a way to move between
records, like a combo box where the user makes a selection. But any code in
that combo box's AfterUpdate event will not be executed if the user moves
between records by using the mouse scroll wheel. You can see there are many
possibilities.

Alternatively, could someone have opened the table and modified the record
directly? Splitting a database doesn't really provide much security.

Carl Rapson

 

[Douglas J. Steele]

I've never heard of records changing by themselves.

Are you sure no one changed the data from outside of your application?

Are you sure your audit logging is complete?

 

[Guest]

I would appreciate if we could return to this conversation on Monday. I
built on this database from home as a side-job.

This is the method I used:

http://allenbrowne.com/AppAudit.html