This is just a wild thought as I do not know the details of what you are doing.
Maybe look at a transaction process around the routine, where you set the transaction level to the lowest. When operating in ODBC you need to deal with RDBMS logic more that U2 for file processing. To get a clean read of a database file, the theory is that you need to lock the file to prevent others updating until you completed a series of reads. Ie if you wanted to total the General Ledger File, it is possible, that while you are reading the GL file, someone else Debit an account you have processed and Credits account that you have not processed, which would make your report not balance, hence why you should lock the file in this type of situation even though you are just reading. By default ODBC might lock that file, it maybe also caused by the ODBC parameters you set up in the calling routine. Words like exclusive, means I have to lock the file. As your routine is not handling an environment like this it maybe causing a fatal for an unexpected expectation. Regards David ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
