Guest was actually me forgetting to login..
Are you saying that embedding a commit is not supported - in lieu of using the COMMIT() command?
That is exactly what I was saying. It's what the documentation says
I can't imagine that ProIV would have provided (and documented) a command like COMMIT() if its use were forbidden... My understanding would be that if you use the COMMIT() statement you are allowing ProIV to handle the transaction processing.
Ah, we're slightly at cross-purposes I think.
COMMIT() is of course supported and allows ProIV to handle the transaction processing but SQL..COMMIT..ENDSQL is expressly forbidden and is not equivalent (I think because ProIV does not necessarily parse the SQL and therefore will not know a transaction has been terminated.. which is a BAD thing.)
That being said, we have also not experienced any problems, other than the same issues that would probably arise using the commit() logic statement, ie trying to update a record no longer locked that others have modded.
I think the problem is that if you use SQL..COMMIT..ENDSQL then even running with SQL_TRANSACTION_ERROR=Y won't trap the problems whereas if you use COMMIT() it should..
Edited by Richard Bassett, 13 July 2005 - 05:29 PM.