Jim,

No argument from me over the documentation that comes with VFP. I do appreciate your assistance here. The SET in the example I believe is just a part of the Update-SQL command. As for #2, I can't recall ever using nested transactions. Mine are typically short enough for one level. I did a lot of work some time ago with Digital's ACMS which was a transaction mgr but it didn't support multiple levels.

Your summary hits the nail on the head. A friend of mine is trying to pick up VFP and needless to say, is having a "fun" time at it.

I have managed to solve the dilemma. We all know that a form is not really in existance until after the .Init fires. This form typically retrieves a record for display during that time. I've found that as long as I issue the RLOCK() after the form is "real", then things seem to be fine. It's just not going to happen on that initial start up.

Steve