Form or Table corruption??? (Access 2003 (SP2))

Topic

New Reply

Edited by HansV to provide link to post – see Help 19

A client of ours is running Windows XP (SP2) with Office 2003 (SP2) on all their PCs. They are experiencing a problem with one of our databases, whereby when they use a reasonably simple subform to input data into a table, the following error message is encountered when they try to tab out of the record (to move to the next available record): –

Reply | Quote

Replies

Try creating a blank new database and importing as many database objects from the problem database into the new one.

Reply | Quote

Oh yes, forgot to try that! I have just importing all the objects into a new database, but the problem still exists! Thanks anyway though!.

Do you or anyone else have any more thoughts/ideas?

Reply | Quote

You state that there’s an identical database that doesn’t have the problem. Are you absolutely sure that the problem database doesn’t have something different, for example extra code? (Some VBA code can make the jet engine believe that the data have been manipulated by another user). If not, I fear that the problem database is damaged beyond recovery.

Reply | Quote

We had a very similar problem. It turns out that the recordset that the form was based upon was being invoked up to four times by other operations that got triggered within the form. Also, there was some circular coding, where the “on activate” event was being called over and over. This poor coding didn’t seem to bite badly when the database was in ’97, but, as soon as we converted it up to XP, the problem became chronic.

The solution was to try to streamline the code, and issue record “saves” prior to bopping out to another form that used the same recordset.

thx
Pat

Reply | Quote