>>Somehow people think that a logical transaction covers for one table only.
>>So what if there are 20 ? and I don't mean some form on a logical view, but just a generative process working through the RI.
>
>Well, this is what I was thinking of. When I had control of things, I would just UNLOCK after I had dealt with everything.
>
>But now, I think I'll have to join a strong religion or something, and let God decide what's best !

Well, sorry, I don't trust that. Possibly He is more far in IT, but no, please let me be in control. Exactly as you say.
Also exactly the same is the UNLOCK issue.

IMO VFP's normal native use (and I don't mean TableUpdate()) outpowers the fashions of today.
As I said elsewhere, I am right in the middle of moving to the remote DBMS, and you can bet your life on it, that I will create something with the behaviour of native VFP. Foolproof that is.

It is not that difficult at all, but what *is* difficult though, is the traject of finding out that all what you are used to just isn't possible anymore. The books don't eloborate on it, you know.

But I know it now; it isn't there. So here we go, and do it ourselves.
How in the world could I let encounter the spoiled user with something like "just try it, when it all doesn't work, it's rolling back. No problem, all consistently !".
Again, come on.

But I guess the Bills & co (Oracle etc.) know better.

um abraço (must be applicable here)
Peter