Craig,

Things have progressed well so far and I've gotten to the point where the DLL works fine locally so I got it installed on the server through component services and I can now instantiate it from my workstation properly. One problem I'm having that is not an issue when I'm using the same DLL locally: I have an object in my application that I'm trying to pass to my DLL so I don't have to create a bunch of custom properties that hold identical data in my DLL. So I create a property in my DLL called goStat and once I've instantiated my DLL object I assign my object in my application to the goStat property. The problem is, the object appears to be properly assigned to the property, but then seems to go out of scope - for lack of a better term. In other words, I can do this process in the command window and watch the debugger and see the object appear as a property in my DLL with all of it's properties, but then if I click on another variable in the debug window, the property loses it's drill-down and is reset to a value of (none). Is there something special you must to do properly assign an object to a remote DLL?

One other question I have is the process involved in updating a DLL that has already been installed on the server through component services. If my DLL is modified, can it be updated simply by copying over the DLL and TLB files or do I need to stop the component and reimport the DLL as I did when it was first installed.

Thank you for your time,

Tim

PS - The articles on your website have been very helpful in this process.