>Bill, what sort of "unhappy" things happen when the resource is on. Our app runs locally on workstations with only data accessed across the wire. So each Workstation has its own copy of foxuser. Does this keep us from being affected by these issues (because there is a local copy)? Also, since the .exe runs locally does VFP just look at startup dir for the foxuser.dbf, or could it possibly being trying to access a net copy?
>
>thanks to all

Since you are running everything locally I would expect that all would work fine. It's just that since VFP opens Foxuser exclusively, in a multi-user environment that could cause problems. I personally don't use foxuser in applications. Settings ( like form size, position, etc. ) are stored in DBF's and restored programmatically by my application object.

Bill