OCX Isolation

[gofrozen]

I'm trying to figure out a way to allow my application and a third party application to use different versions of the same OCX file without having to manually reregister the appropriate OCX each time. Currently the OCX associated with whichever application is installed last will be take precedence with both apps. My application's OCX resides on a network drive and it is registered locally during setup. The third party software application OCX resides in the system32 folder.

I listed my app's OCX file in the'ExcludefromKnownDLLs' registry entry in hopes of searching the exe and current directory first, but this did not isolate the OCXs. Does anyone know of a way to force WinNT to look at a specific OCX even when a newer version of the OCX was recently installed in the system32 folder?

Thanks for the help.

Ed