>>I need to have an object that is accessable from any instance of the program on our LAN. In other words I need to instantiate an object at login of the first user to execute the .exe from whatever workstation, Win95, Win98, or WinNT. The program will reside on an NT workstation or NTServer. Subsequent executions of the same program will need to access methods and properties of the original object. Then, when the last user quits the program, the object will be released. My question is, before I create a mountain of code that doesn't work across platforms, do all the platforms mentioned use the memory space on the box where the program resides? Or do some use local memory space? Also, is the scope of an object limited to the application that created it even if declared public? I've never tried this before, but I noticed with one of our 2.6 projects, we had to copy the foxlibs to the local machine in Win98 but do not have to do this with Win95. This makes me wonder if programs are
>>executed differently across the LAN after Win95.
>>
>
>Create a DCOM Object, and add a reference count property to it; have methods to attach (increment) and detach (decrement) reference counts. Whenever detach decrements to 0, force the COM server to shut down.
>
>In VFP, issue a CREATEOBJ() to instantiate the out-of-process server (or attach to an already running instance) and then invoke the attach and detach methods as appropriate.

Is there any documentation on how to create an out of process server?
Never done it... Is there a class available in NT or VFP?

Eric K.