FIX: Wrong Result Using RtlMoveMemory to Copy Nested UDT with Fixed-Length String Array (262667)
The information in this article applies to:
- Microsoft Visual Basic Professional Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q262667 SYMPTOMS
If you copy a nested user defined type (UDT) with a fixed-length String array to a fixed-length String by using a RtlMoveMemory API call, you may not get the right result.
RESOLUTION
This problem can be solved in one of two ways:
- Install the latest service pack for Visual Studio 6.0.
- Use an intermediate byte array. That is, first copy the UDT to a byte array and then assign the byte array to the fixed-length String.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in the next service pack for Visual Studio 6.0. For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base: 194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed To download the latest Visual Studio service pack, visit the following Microsoft Web site: REFERENCESFor additional information on the VarPtr function, click the article number below
to view the article in the Microsoft Knowledge Base:
199824 HOWTO: Get the Address of Variables in Visual Basic
Modification Type: | Minor | Last Reviewed: | 12/12/2005 |
---|
Keywords: | kbAPI kbBug kbfix kbVS600sp4fix kbVS600sp5fix KB262667 |
---|
|