Referential integrity issues

I4GL 7.20.ud6 IDS 7.30.uc7 HPUX 10.20 I've been told of a real weird problem within a piece of our 4GL code. We have some home-grown code that starts a transaction, inserts a master record, checks the return code, then inserts multiple detail records, checks the return code and commits the transaction. Any problem with the inserts will cause the error routine to pop a window, warn the user, and rollback the transaction. Referential integrity is active between the tables. Most of the time, the code acts normally and all is well. Every now and then, we'll get the dreaded -691/-111 errors. Apparently, the master insert doesn't happen, but SQLCODE doesn't show that fact. (We have checked the master table while the error is on the screen; no master record.) Any ideas? This is causing a few gray hairs, and I don't have many left to spare . . . . 8-) -- John Carlson Informix DBA WHSmith USA #include std_disclaimer.h /* These are my opinions, not my company's opinion */