Mike:
Another thing to watch out for is the transaction constraints Brian
mentioned. Where I've seen this most often is if your application has
programs that add new records to a file without first getting a record
lock with a READU. UniVerse lets you "write in the dark" if you want
to. (Whether that is right or wrong is a different debate, but it
happens.) Since triggers force transaction constraints, this will then
fail. I don't remember the exact wording of the error message,
something about "ISO isolation level."
Regards,
Clif
--
W. Clifton Oliver, CCP
CLIFTON OLIVER & ASSOCIATES
Tel: +1 619 460 5678 Web: www.oliver.com
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
