Hi Tim

> 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.
> ..
> Is there something special you must to do properly assign an object to a remote DLL?

I don't think this can be done: in order to convert the VFP object to a COM object that can be marshalled across processes the properties go missing. Once the properties have been referenced they seem to appear but on the whole passing objects to COM+ seems too unreliable.

> 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.

If you haven't changed the interface - properties, methods, their parameters - you might be able to drop in a replacement DLL, but I would recommend removing the old and adding the new to the COM+ package as usual in order to avoid compatibility issues. If the component is in use you won't be able to update it on the fly anyway.

Regards

Stuart Dunkeld