VB6 "Make Project" Error on Creating .exe file 1

[tg0001]

It seems that when I select the "Make Project" option in Visual Basic 6.0 (installed on a DELL PC) to create .dll files and an .exe file for a Visual Basic project group (.vbg), the following occurs:

1) The .dll files are created successfully (i.e. The "Compiling dll..." tasks for the files runs successfully.)
2) The .exe file is not created successfully. Instead the "Writing exe" tasks stops in the middle of running and displays an error in a window. The error is the following:

Visual Basic has encountered a problem and needs to close.
We are sorry for the inconvenience.

Please tell Microsoft about this problem...

...(and so on)...

After I press the "Don't Send" button on the window, the following error displays in the "VB6.EXE - Application Error" dialog box:

The instruction at &quotx00435432" referenced memory at "0x000000b". The memory could not be "read". Click on OK to terminate the program.

I then press the "OK" button on the window and Visual Basic 6 closes.

I do notice that the .OBJ files for the form (.frm) files in the Visual Basic project group are generated in their respective project folders prior to the error occurring.

What is causing this Visual Basic 6.0 error? Is it caused by a memory problem? Is it caused by a software compatibility problem between Visual Basic 6.0 and Windows XP?

How can this error be resolved?

Please let me know what you find out.

Thanks for your assistance.

 

[sciophyte]

there are not many problems with vb under xp, i use it all the time. first thing, make sure you have the latest service pack.

You can try to create a new project with the same structure as the old one (all the same forms and modules) and copy and paste all the code into the new project and try to compile that.

if all the obj files are being created as you said, then another possibility to look into is running the compiler from command line to compile it.

if you have 3rd party component references/controls try removing those and commenting out the code with those objects and see if it compiles normal then re-add and see if it will crash again.

 

[JeffTullin]

Couple of other things I have seen cause this kind of behaviour in one of my projects:

a) Compiling while using the Internet.
b) Compiling to native code (switched to pcode and it worked fine)