ACC2000: Unexpected Behavior When You Try to Save a Stored Procedure That Has Numerous Syntax Errors (266728)
The information in this article applies to:
This article was previously published under Q266728 Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access project (.adp).
SYMPTOMS
When you try to save a stored procedure in an Access project, you see one of the following behaviors:
- You receive a message box that has no OK button.
- The stored procedure appears to be saved, but when you close the designer, the application is unavailable for use.
After you experience either of these behaviors, you have to press CTRL+ALT+DELETE to quit Microsoft Access. As a result, the stored procedure is lost.
CAUSE
There are too many errors in the stored procedure.
RESOLUTION
When this problem occurs, you must re-create the stored procedure.
To avoid this problem, when you are designing a stored procedure, copy and paste the stored procedure into Notepad, and then save it as a text file before you try to save the stored procedure in the SQL text editor.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem no longer occurs in Microsoft Access 2002.
Modification Type: | Major | Last Reviewed: | 6/30/2004 |
---|
Keywords: | kbbug KbClientServer kbfix KB266728 |
---|
|