missing records

[eggwater]

I have a number of users using a database. They input data using a form. The database is split into Front End, Back End and i'm pretty sure that the record locks are set correctly and the users should not be able to delete records unless it was by accident evn so it would have to follow a number of coincidences for a record to get deleted.

Is it possible that new records could not be saved or that old records could go missing.

It would therefore appear that out of about 1000 records 10 or so have gone missing.

I am of the assumption tht this is some kind of user error , but the users are swearing blind that they entered the data. They actually write down the autonumber ID on top of the forms they are entering data from.

has anyone had a similar problem or is there anything that could cause this to happen?

 

[The_Doc_Man]

As a precaution, add some code on your form in the AfterUpdate (of the form, not of any field) to requery to recordset for that particular AutonumID. If this query works, you have some certainty that the update occurred. If not, you have found a data loss event. At least you would be able to know that such a loss occurred and you could question your users.

Another thing you could do is keep a log file of who entered what record when in a separate table. This log would enable you to find out who is dropping records. If it is spread out, you have a systemic problem. If it is concentrated on one person, maybe it isn't systemic.

If you allow the user to proceed to the next record without verifying storage of the prior record, the prior record could be overwritten. If the user doesn't click the button for a new record, but instead just starts entering data, all that is happening is that the current fields are being overwritten.

One thing I have done in the past is to set an interlock in the code so that if a user tries to leave a new or modified record without storing it, I prevent them from closing the form or navigating off of the current record. They have to either click the COMMIT button or the CANCEL button. I also put some safety code so that if a user is about to change a non-blank data field that participates in some other keys, I put up a message box that forces confirmation of the intent to change the field. If they say no, I pop up another box that asks if they want to enter a new record. If they say yes, I capture each text box, do an Undo on the current record, then create a new record and repopulate the text boxes with the new data. But this does require some persistence on your part. Not to mention some meticulous programming.

 

[eggwater]

thanks fella that is really useful info.

I'll track down the culprit... I'm pretty sure i know who it is.

My problem is doing work on a database I haven't dicked around with for about 6 months.

cheers

have a nice weekend.