Not bored - just nonplussed. We do this the 1st way you talekd about a lot from Serviced components and it works fine.

Is it the lciense file for the OCX. I think the corresponding OCA has something to do with this but what do I know...

Here's waht I use - it also late binds to a Enterpise Serviced component in COM+ - and calls the VersionProperty on the class represented by the Prog ID... // Create a Crypto Manager - Create the Type locally Type tEngine = Type.GetTypeFromProgID("Collaborator50.EQOSCollaborator", vstrAppServer, true); // Create an Instance of Type objEngine = Activator.CreateInstance(tEngine); // Make the call object objVersion = tEngine.InvokeMember( "Version", BindingFlags.Public | BindingFlags.GetProperty, null, objEngine, null);

Somewere on this very site - name eludes me though

We use System.Runtime.Marshal.Cantremembetthisbit.ReleaseComObject() which seems to clean up on the spot.

Do the remoting components make use of any unmanaged resources / should or do you implement the IDispose interface?

What was the COM exception?

Dont think you can.