PRB: Visual Basic Module Shuffle Looks Like Entire File Change

 Last reviewed: March 11, 1997
Article ID: Q154828
The information in this article applies to:
  • Microsoft Visual SourceSafe, 16-bit and 32-bit, for Windows, version 4.0
  • Microsoft Visual Basic Standard and Professional Editions for Windows, version 3.0
  • Microsoft SourceSafe for Windows, version 3.1

SYMPTOMS

In Visual Basic version 3.0, the code modules contained in a form are occasionally reordered. This problem is very noticeable when the form is under SourceSafe control because it appears as if the entire Visual Basic form has changed.

This causes problems for SourceSafe because when this reordering happens there is no easy way to see just the code changes that were made by the developer.

RESOLUTION

Visual Basic 4.0 does not reorder the modules in forms.

STATUS

This behavior is by design.

This problem was corrected in Visual Basic version 4.0 for Windows.

MORE INFORMATION

This reordering of modules in Visual Basic is not a common or consistent occurrence. There is nothing that can be done to prevent this from happening in Visual Basic 3.0.

Keywords : ssafe kbinterop kbprb
Version : 3.00 3.10 4.00
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.