ACC2002: Access Quits Unexpectedly When You Try to Open the Visual Basic Environment from a Database Object (302784)
The information in this article applies to:
This article was previously published under Q302784 Novice: Requires knowledge of the user interface on single-user computers.
This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).
SYMPTOMS
When you try to open the Visual Basic Environment (VBE) from an object that has a semicolon in its name, Access may appear to stop responding and quit unexpectedly.
After you restart Access, you may find:
- The object can no longer be opened.
- The object cannot be renamed.
- The database may be in a corrupted state.
CAUSE
You are trying to open the Visual Basic Environment from an object that was created in an earlier version of Access, that has a semicolon in its name, and that has its HasModule property set to Yes.
The semi-colon is a reserved symbol for Microsoft Access, and Access 2002 does not permit object names to contain reserved symbols. If you use a reserved symbol to name an object, you may see unexpected behavior in the application.
RESOLUTION
Remove the semicolon from the object name in the earlier version of Access before you convert or open the database in Access 2002.
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: | 9/26/2003 |
---|
Keywords: | kbbug kbpending KB302784 |
---|
|