Hi, Paul.
No, in my case that's not the problem. It's really with the activeX control (finally even found the vendor's reference to it). Interesting solution you had--did you tell us that the ocx was in a subdirectory? I don't remember. But, it would be a good question to ask folks when they post problems with ocx.

Regards

>I checked out the Microsoft Knowledge Base and found an article that took care of my problem and thought I would tell you about it in case you are having the same problem. The article # is Q160771. Basically it says the .ocx file needs to be in the same folder as the executable in your distribution tree. I had my ocx in a subfolder called libs...as soon as I moved it into my app root
...snip