Where I work, we have developed an application using VB 6, developed on Windows 98 and NT. It contains 107 forms, 6 .bas modules, and 44 crystal report .dsr forms. When we run the application from the IDE under windows 98, it looks like it runs through all the forms and the project explorer window flickers but there's no problem running and debugging the application. Under NT 4.0, this doesn't happen. Recently, I upgraded my development machine to a laptop that runs Windows 2000. When I run the application in the IDE, the project explorer window flickers and it appears to be running through all the forms. Worse than that though, when I exit the application, and click on either of the project explorer scroll bars or the code window scroll bar, I'm thrown out of VB altogether. Sometimes I get an error message:
VB6.exe - application error. "The instruction at ... referenced memory at ... could not be read." Often though, there's no error message. VB just closes.
I would really appreciate it if anyone has any idea what could be causing this and how I can solve it.
VB6.exe - application error. "The instruction at ... referenced memory at ... could not be read." Often though, there's no error message. VB just closes.
I would really appreciate it if anyone has any idea what could be causing this and how I can solve it.