- Local time
- Tomorrow, 07:35
- Joined
- Jan 20, 2009
- Messages
- 12,895
Changing names of objects with the AutoCorrect regime enabled seems the most common cause. I have certainly experienced it at a control level on forms. Usually pasting the sql fixes that.
I have also had it happen when renaming a form. The database lost its connection to the VBA project. Despite still connecting in design view the events would not run. The really bizarre aspect of this was that it did not lose them all at once. Some buttons still worked but any procedures they called wouldn't run.
In this case I had to export to a new database. However I have heard reports here of the corruption going with an export. In that case copying the objects on the form to a new form fixed it.
I don't know for sure but I gather that AutoCorrect does not actually change the names but uses some kind of symbolic reference behind the scenes.
Some deveolpers refer to it as AutoCorrupt and strongly recommend it be turned off.
I have also had it happen when renaming a form. The database lost its connection to the VBA project. Despite still connecting in design view the events would not run. The really bizarre aspect of this was that it did not lose them all at once. Some buttons still worked but any procedures they called wouldn't run.
In this case I had to export to a new database. However I have heard reports here of the corruption going with an export. In that case copying the objects on the form to a new form fixed it.
I don't know for sure but I gather that AutoCorrect does not actually change the names but uses some kind of symbolic reference behind the scenes.
Some deveolpers refer to it as AutoCorrupt and strongly recommend it be turned off.
