What is the maximum exe size??

I am getting some strange unexplained errors in my program.

The exe is just over 2M in size. Is this a problem?

What errors are you getting exactly? The exe size should not be a big deal.

EXEs > 2MB isn't uncommon.

Are you getting any "This program has performed an Illegal operation and will be shut down" or "Memory Fault in " kind of errors. If so, please check for your program for any memory leaks.

I have seen somewhere the Exe size > 15 MB...and working still...so that is not a problem

Run-time error 5. Invalid procedure call or argument.

I have put some MsgBoxes to try to locate the error and it. It appears to come in a simple call like this " radioCharge_KeyDown Index, 13, 0". Up until this week, the program worked perfectly - I have just been adding a few enhancements.

I have no problems when I run through VB6 with vbp.

Quote:

---

Originally Posted by Supremus

Run-time error 5. Invalid procedure call or argument.

I have put some MsgBoxes to try to locate the error and it. It appears to come in a simple call like this " radioCharge_KeyDown Index, 13, 0". Up until this week, the program worked perfectly - I have just been adding a few enhancements.

I have no problems when I run through VB6 with vbp.

---

Are you using error handling everywhere? That seems like it would find it for you. MZTools can help you easily add them in enmass.

My error handling ability is pathertic. I do have MZ tools and will look at that.

I used the Package and Deployment wizard and received this error message but I can't understand why it wants that file. It's nowhere on my system ...

*** ERROR: The file 'c:\DOCUME~1\Peter\LOCALS~1\Temp\msftqws.pdw\$(DLLSelfRegisterEx)' could not be registered because it was not found.

I am getting errors in different places if I remove one suspect sub routine. It tells me a variable isn't set, but it is set and doesn't change.

I added a form with a cmd button then removed all the files from my program, and compiled that. I then added all the files again and still had the problem.

It doesn't make sense to me.

Perhaps something that doesn't need to be there got placed in your setup and installation file. I would go through that carefully to see exactly what is there. If you see something that you feel doesn't belong, remove it and see what happens (you can always put it back.)

Thanks Hack.

I have just done a lot of googling and it is a known problem. Msftqws.pwd is actually a temp directory created by the package wizard.

I have narrowed down the routine causing the problem and am going to rewrite it to see if that eliminates the problem.