Environment vs. EXE

[mikef]

I have a program that is producing a Windows Illegal Operation error in itself when executing a certain line of code.

When I run the program in the environment, the variables contain the right numbers and the program executes properly.

Then I compile and run the stand-alone EXE and when it runs this exact operation I get a Windows Illegal Operation Error. The program caused a fault in itself at registers etc. etc.

Anyone know why it works flawlessly in the environment, but errors when run as a stand alone????

Any leads or information would be helpful and greatly appreciated...

thanks!

[nishantp]

Just a thought, but if you unchecked any options in the advanced optomizations in the compile options, check them again. That may be the problem...

[mikef]

Thanks for the info. I am not multithreading. There is however and STOP statement in one part of my code, but this code is not executed at anytime when the error occurs.

Also, it seems that the error is occuring when using the CALL statement. I put a break where it was faulting and stepped over that line... but it crapped out the same way when it hit another CALL statement.


thanks again...

any help appreciated!!!

[mlewis]

What are you CALLing?

[mikef]

I am calling another public sub.. like so:

Call Circular

the other one it crapped out on when I stepped over the above one was this:

Call frmMain.CleanUp


thanks again...

[mlewis]

Try erasing CALL and just writing the sub name.

ex:

Circular

or

frmMain.Whatever

[mikef]

i'll try it... thanks again!!