ACC2000: Module Disappears After Running Code (223199)
The information in this article applies to:
This article was previously published under Q223199 Moderate: Requires basic macro, coding, and interoperability skills.
This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).
SYMPTOMS
Running code in a module may cause the module to disappear.
CAUSE
When you are running code in a new, unsaved module and the code includes the programmatic creation and saving of another new module, the module that contains the running code disappears.
RESOLUTION
Because existing (saved) modules are not affected when new modules are created programmatically, ensure that the active module is compiled and saved before you run it.
Unfortunately, there is no way to recover a module that has disappeared because of this issue.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 6/28/2004 |
---|
Keywords: | kbbug kbpending KB223199 |
---|
|