>>Hi all,
>>We just got VFP7 installed and my first bit of confusion has already come up.
>>When we try to open the Table Designer on an existing table, Stand Alone env, the table opens ReadOnly, which is kind of useless. We've changed the Options to default Open Exclusive, but the Table designer still opens the table ReadOnly unless we key in USE table1 EXCLU in the Command Window. I didn't have this problem in VFP3 or VFP5 that I remember.
>
>I looks like VFP 7 ignores SET EXCLUSIVE setting and opens tables SHARED when request to open table is implicit (not thru USE commnad). For example, issuing BROWSE or MODIFY STRUCTURE w/o table open in the current work area always opens table in shared mode. I don't know if it's a bug or a feature.
>
>You can fill a bug report at http://support.microsoft.com/Support/vfoxpro/report/report.asp

Hi Sergey,

The problem is even wackier than I thought. We installed VFP7 on 5 workstations (as stand alone) sharing the same LAN. We all have FPW2.6 installed locally, but use a folder on the LAN for resource location.

It appears that VFP7 went out and looked for a resource folder (by default) and found one on the LAN in a FPD folder (foxuser.dbf). (the FPW resource is set ReadOnly). As each of us turned on VFP7, the Command Window history showed what we ALL were doing. Appears we were all sharing the same foxuser.dbf.

I modified my Options to point elsewhere, but VFP7 insisted on changing the Resource Directory back to the folder on the LAN until I created a local folder. Part of the goofiness was that the default VFP7 shortcut created by VFP7 installation would not let me change the Target to include the "-cc:\myvfp7\config.vfp" extension. I had to create another shortcut. Now the Options in VFP7 stay as I set them.

Am I the only one to notice this behavior? Seems odd that VFP7 would look through the LAN for a resouce folder rather than use one it created locally. Am I making sense?