Geek asks and answers

Errors occur after database corruption

I had a split database that worked fine on a client machine for more than 2 years. Due to unknown circumstances, the database was corrupted. And the deletion of several damaged records has been fixed.

Now the front part starts to produce the following errors:

2147352567

2448

These errors will be thrown individually if the user performs a specific action.

How can it be that these errors suddenly began to appear when everything is working fine?

Not wanting to drown out this question using code, the premise of forms when an error occurs is as follows:

The form is open, and the Excel spreadsheet can also be open, which links to this record.

When saving / closing the excel table, the corresponding field in the database record is updated.

User decides "Refresh Excel Spreadsheet" or "Save and Close"

Errors occur in Before_Update events on the access form

Is there a reason why these errors could occur because it seemed like a perfectly functional system?

Thanks in advance for any help.

+3
source share
1 answer

I solved the problem by including the appropriate update record in the code:

If Me.Dirty = True, then Me.Dirty = False
End if

I still don’t understand how the errors arose, although after the database went bad? Forms / buttons / actions will be used daily by users during their working week for more than 2 years.

+3
source

More articles:


All Articles