> >
> > Hi again Cetin,
> > Thank you for explaining this to me. I do not see the "IsExclusive()" command in the VFP9SP2 HELP list so I did not know it even existed. I now see it documented on MSDN as a VFP function.
> >
> > Turns out what I was doing was:
> > 1. Double-clicking on a vfp table (which was part of main.dbc) to launch VFP so the default directory would be where the database/tables were located.
> > 2. Issue the USE command to close the table (since it would be opened exclusive)
> > 3. Issue the OPEN database main SHARED command
> >
> > Doing the above results in a .T. for isExclusive(). If I launch VFP by clicking on the VFP icon, change my default directory to c:\database (I don't really need to change default) and then OPEN database main SHARED I get a .F. for isExclusive().
> >
> > So, doing step #1 above actually must open the database even though it does NOT appear in the details when I do a DISPLAY STATUS!!!
> >
> > I will now test my asp code again...thank you,
> > Ron
>
> Ron,
> You can easily solve it (do this once):
>
> Modify command home()+'config.fpw'
>
> Add this line and save:
>
> exclusive = off
>
> Then by default VFP wouldn't open its tables exclusive.
>
> (Or you can do via menu:
> Tools\Options\Data - Uncheck "Open Exclusive")
>
> Cetin Basoz

Cetin...thank you again for ALL your help! After my last reply to you, I did find isexclusive() in the VFP HELP file by scrolling thru all the functions. Simply typing "isexclusive" in the index did not find it.
Also, I thank you for pointing out the ways to turn off the set exclusive. I believe my client may have some reason for having it set "on" so I will check with them. Locally on my dev laptop I have not had to worry about this.

My ASP code works just fine now in shared mode. Thank you, Ron