>I just did some experimenting, and now I don't know what to believe!
>Here's what I did:
>1) Open two VFP 5.0 sessions on the same machine.
>2) SET EXCLUSIVE OFF, on both.
>3) USE MyTable, in both sessions (same table used).
>4) In one session, do an INDEX ON Expr TAG Expr - no problem.
>5) In the other session, table is still modifiable. Try SET ORDER TO Expr - error: 'Table has no index order set'. Close this table with USE and try to re-open - error: 'File access denied'.
>It's like the table went from SHARED TO EXCLUSIVE use in the first session, because of the INDEX command!

No, apparently I don't know anything about it! < s > I would have expected what I think you did, an error in the first session when you tried to INDEX ON. I come to the same conclusion you did. It seems that the INDEX ON command in the one session automatically re-opened the table for exclusive use. Something I never would have expected it to do.

Someone who knows about this, please jump in! Knowing how indices work is (IMO) the single most important knowledge for a developer to have about FoxPro. From Dr. Dave's first release, FoxPro's indexing has been its greatest advantage over its competitors, providing all the speed and power FoxPro has (rightfully) bragged about all its life.

Help,