An error in EXE which doesn't happen in Design Environment

[Dwaine]

Okay. As a preface, I've been doing this for over 5 years, and this has got me stumped.

I'm getting an error: Run-time error '5': Illegal Function Call when I'm running the .exe . I do not get this when running in the design environment (Start with Full Compile). I cannot track down what or where the error is caused.

As a given, all 'on error resume next' statements are commented out. I'm using Option Explicit.

In order to attempt to trap it the old fashioned way, I have msgbox's in certain places, but the oddest thing happens. No matter where I put my msgbox's I still get the error, but the msgbox is behind the error dialog box. I can still click on 'OK' on my msgbox and the program terminates.

Kind of a tough one to explain, but even tougher to figure out. Anyone???

[csammis]

Could you post a snippet of the code so we can better understand the problem? Illegal Function could be from a few reasons.

[Dwaine]

Actually, that's the deal... I can't isolate which piece of code is causing the issue. I have done error trapping in every sub or function (not resume next) and it won't trigger. Stepping through shows no errors anywhere. But, as I said, running the standalone exe generates the error when attempting a particular function.

[jim mcnamara]

Any function or just a

particular function

?

[Dwaine]

It all had to do with showing msgbox or other vbModal forms within the context of a current vbModal... Still wierd, but at least I figured it out. I don't understand why it wasn't happening when running in my ie.