>>Paul,
>>
>>If you have two clients using two different instances of a VFP server from two different workstations using DCOM the publics will collide with each other.
>
>That's because the VFP dll is run, in fact, on the server and regardless on how many clients use it, there's only one process running the dll. So, in fact, there's only one VFP app running.
Vlad,

You are wrong on this. Ther are two different stations each with their own fox server that both happen to be running on the same network server machine. The publics will clobber each other.

Station 1: Create a VFP server object on the network server machine

Station 2: Create another fox server (doesn't even need to be the same class) on teh network server machine.

The public vars of station 1's server can clobber the public vars of station 2's vars.

Notice that I even said these can be two different VFP classes. This si a problkem of how VFP handles the runtime with DCOM and the proitection or lack thereof for the VFP memory space. To make a long story short, don't use PUBLIC and none of this is ever an issue.