BUG: VB Fails When Editing Modules That Are Interdependent (190198)
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows 6.0
- Microsoft Visual Basic Professional Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q190198 SYMPTOMS
When your project contains modules that are heavily dependent upon each
other for variable definitions (such as a constant being the type of
another module, or passing a UDT defined in one module to another), editing
one module will gradually cause Microsoft Visual Basic to fail.
CAUSE
The problem is caused by an illegal circular dependency cycle between the
modules.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this bug and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
Modification Type: | Major | Last Reviewed: | 5/13/2003 |
---|
Keywords: | kbbug KB190198 |
---|
|