Hello:

I use transaction processing. The general rule that I follow is:
if I am updating multiple tables on a single action (e.g., Click
on Save button) by the user, then I use trasaction processing.
These processes are more batch oriented and generally the table
updates are dependent on each other.

For a single table update or a set of one master and one child
update I tend not to use transaction processing, since I feel
that would be a overkill for the task.

On the other issue regarding transaction processing, you must
unlock table or record yourself and explicitly if you are
locking them within the BEGIN TRANSACTION - ENDTRANSACTION
section. It is not a common practice to leave upon VFP to lock
a record, table or file header with commands such as APPEND
BLANK.

Hope this helps.

Rahul C.

>I recently tried using transaction processing on a form with two child grids. The Rollback command made cancelling multiple actions easy to program. However, I found that transaction processing locks the file even for new record adds by another user. I contacted Microsoft and they confirmed this. They said that transaction processing had not been implemented with an eye toward individual record handling. I had thought that only existing records being modified, or a single append blank record, would be locked by transaction processing. I was wondering if anybody had tried using trnasaction processing and came up with a way around this.
>
>TIA
>
>Jim Boho
>Univ of Wisconsin