Dick,
We've seen this 'intermittent' problem also. It was finally traced to times with heavy server use, and was almost completely stopped when a very active print server was moved to another server. In a few cases we did have to program checks to be sure the procedure was complete.

HTH
Barbara

>I am having an elusive problem with a customer running several stations on NT server network. Sometimes (there's that awful word) one of the tables in a "save" routine is not getting updated. It may be added or edited or deleted. The save method is a custom method where several TABLEUPDATEs are wrapped in a transaction. All tables are Optimistic table buffered.
>
>The "END TRANSACTION" line is the last line in the method and the form actions go on to do other things. I'm beginning to think that the form goes on its merry way before the transaction is really finished doing its thing. Another clue to this occurred today when one user got an error message that said "command cannot be used within a transaction" or some such paraphrase of that.
>
>Do I need to explicitly program a delay after the "END TRANSACTION" code? Is this an issue with the network not finishing it's task before the form wants to use the tables again. Most of the PCs at the workstations are fairly robust. Can anyone shed any light on this?
>
>Dick Harrold