The information in this article applies to:
- Standard, Professional, and Enterprise Editions of Microsoft Visual
Basic for Windows, 16-bit and 32-bit, version 4.0
SYMPTOMS
An application error occurs when you save a module if you change the
module's name in the property sheet and use the keyboard shortcut CTRL+S
to save the module before pressing the ENTER key. This behavior does not
occur when you save the module by clicking Save File on the File menu.
STATUS
Microsoft has confirmed this to be an issue in the Microsoft products
listed at the beginning of this article. Microsoft is researching this
problem and will post new information here in the Microsoft Knowledge Base
as it becomes available.
WORKAROUND
The following are ways to work around this behavior:
- Change the module name and press the ENTER key before saving the module
using the shortcut key CTRL+S.
-or-
- Save the module by clicking Save File on the File menu.
MORE INFORMATION
Steps to Reproduce Behavior
- Start Visual Basic 4.0, or if it is already running, click New Project
on the File menu.
- On the Insert menu, click Module to insert a module into the project.
- On the File menu, click Save File to save the module as TEST.BAS.
- On the module's property sheet, change the name property to Test and
press CTRL+S. An application error occurs with one of the following
messages and Visual Basic ends:
32-bit Visual Basic
Windows NT 3.51-An application error has occurred and an
application error log is being generated.
VB32.exe, Exception: access violation
(0xc0000005), Address: 0x004b788b.
Windows 95-This program has performed an illegal operation and
will be shut down. VB32 caused an invalid page fault in
module VB32.EXE at 0137:004b788b.
16-bit Visual Basic under all operating systems
VB caused a General Protection Fault in module VB.EXE at
003E:05CED. Choose Close. VB will close.
|