Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/171557

From BetaArchive Wiki
Knowledge Base


Article ID: 171557

Article Last Modified on 10/11/2006



APPLIES TO

  • Microsoft Visual Basic 5.0 Control Creation Edition
  • Microsoft Visual Basic 5.0 Learning Edition
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition



This 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"

Clicking OK terminates Visual Basic 5.0.

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:

      Type MyType
         x as integer
         y as integer
      End Type

      Type MyType2
         a as string
         b(6) as Mytype
      End Type
                

Other UDTs suspected of causing the error contained 15 or more elements.

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 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 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.

Keywords: kbbug kbfix kbprogramming kbvbp500sp2fix kbvs97sp2fix KB171557