Article ID: 171557 - Last Review: October 11, 2006 - Revision: 2.2 FIX: Compiling VB5 Applications with Large UDTs May CrashThis article was previously published under Q171557 SYMPTOMS
Compiling a project in Visual Basic 5.0 or compiling a project in Visual
Basic 5.0 converted from Visual Basic 4.0, may cause an error similar to
the following:
"The instruction at "0x77f64d07" referenced memory at "0x0013fff8. The
memory could not be read. Click on OK to terminate the application" CAUSE
Doing Put/Get on large records that contain records, VBA fails when writing
out the GetPut descriptor.
A common trait of the UDTs that cause the error is that these UDTs often contain arrays of other UDTs. For example: RESOLUTION
The only sure workaround is to use smaller records.
STATUS
Microsoft 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: 170365
(http://support.microsoft.com/kb/170365/EN-US/
)
INFO: Visual Studio 97 Service Packs - What, Where,
and Why
For 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:
171554
(http://support.microsoft.com/kb/171554/EN-US/
)
INFO: Visual Basic 5.0 Fixes in Visual Studio 97
Service Pack 2
MORE INFORMATION
The UDT must be very large to cause this problem. However, it is not
strictly size but the types of the members as well. The exact record size
limit is unknown.
APPLIES TO
| Article Translations
|

Back to the top
