How To Avoid "Error 91" when Debugging MTS Components with Visual Basic (188919)
The information in this article applies to:
- Microsoft Transaction Server 1.0
- Microsoft Transaction Server 2.0
- Microsoft Visual Basic Learning Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q188919 SUMMARY
When developing Visual Basic components to run under control of Microsoft
Transaction Server (MTS), if your object uses ObjectContext, you may
encounter the following error when trying to debug them within the Visual
Basic environment:
Run-Time Error '91': Object variable or with block variable not set.
This article describes how to configure Visual Basic to allow you to debug
these components using the special debug version of GetObjectContext.
There are two ways to avoid this error when writing Visual Basic
components. The first is to configure Visual Basic to use a special version
of the object context. The second way is to use the Microsoft Developer
Studio environment.
REFERENCES
For more information on debugging compiled Visual Basic components using
the Microsoft Developer Studio environment, please see the following
articles in the Microsoft Knowledge Base:
166275 How To Debug a Native Code Visual Basic Component in VC++
244457 How To Debug an MTS Visual Basic Component Running Under ASP
Microsoft Transaction Server 2.0 Help; search on: "Debugging Visual Basic
MTS Components"
Modification Type: | Minor | Last Reviewed: | 8/30/2004 |
---|
Keywords: | kbBug kbDebug kberrmsg kbhowto KB188919 |
---|
|