> If we could bundle all the calls into our own exe, any checks against these libraries should find the ones running in our app's process space first.

I think we all understood your question - you want to distrubute one EXE file - no runtime files at all. Besides VB's runtime files, you could install your OCX files in your application's directory instead of the default window's system directory. That way you can have to different versions of the same OCX on a machine. And I think a VB application searches in its own directory before it searches in the system directory for a library. I'm not sure about that.

That way your application will use the OCX in its own directory, not the system one.

I haven't tried this, so I don't know if it will work.

Good luck,

jody