FIX: Problems Binding Controls to Nonexistent Data ControlLast reviewed: December 18, 1997Article ID: Q171805 |
The information in this article applies to:
SYMPTOMSSetting the DataSource property of a control to the name of a data control that does not exist may cause a GPF with the following information:
“Visual Basic 5.0 caused an invalid page fault in module KERNEL32.DLL at 0137:bff78053” STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2. For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q170365 TITLE : INFO: Visual Studio 97 Service Packs - What, Where, and WhyFor a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q171554 TITLE : INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2 MORE INFORMATION
Steps to Reproduce BehaviorTo reproduce the problem, place a data control (either standard or remote) on a form. Set its Name property to "ExtremelyLongName" and set its Index property to 0. Place a textbox (or any other control that can be bound) on the form and set its DataSource property to "Foo." Run the project and the problem will occur. Besides trying to bind a control to a non-existent data control, in order to reproduce the problem the data control must be part of a control array and its Name property must be longer than any name used in the DataSource property of the bound controls. Keywords : vb5all VS97FixlistSP3 VS97FixlistSP2 VB5FixlistSP2 Version : 5.0 Platform : NT WINDOWS Issue type : kbbug Solution Type : kbfix kbservicepack |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |