When a select is being executed, are there any protections in
place against tables being changed while the select is executing?

I think the answer is: For a table that is in a database,
transactions protect against this, but for a free table, there is no
protection.

One possible way around the protection: Can a transaction be
committed while a select is executing? I hope not, but is this
guaranteed? (If it is not guaranteed, multi-table selects could get
messed up.)

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

There are no more protections on SELECT than there are on APPEND
BLANK/REPLACE.

Since VFP applications (and transactions) happen in memory on the
workstations, there is no way for one workstation to know what the other is
doing save for record/file locking that we've been using since dBase II.

Dan

Gene Wirchenko wrote: