The information in this article applies to:
SYMPTOMSWhen you create a stand-alone (compiled with the /o option) executable program that uses overlays and ISAM, your program hangs (stops responding to input) when it attempts to execute an ISAM open statement. However, when you compile the same program to use a runtime module (compiled without the /o option), the program runs correctly. WORKAROUNDTo work around the problem, specify the PROISAMD.LIB file in the objects section of the LINK command, as in this example: LINK MODULE1.OBJ PROISAMD.LIB (MODULE2.OBJ);This forces the linker to pull in all of the object code from the ProIsamD library, so it can run correctly as a standalone program. STATUSMicrosoft has confirmed this to be a bug in the Professional Edition of Microsoft Visual Basic version 1.0 for MS-DOS. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATIONIf you want your program to use overlays and ISAM, you must compile your program without the /o option, so that your program requires a separate run- time module. The following example demonstrates the problem:
Additional query words: VBmsdos buglist1.00 1.00
Keywords : |
Last Reviewed: December 8, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |