DETAILS If a RETRIEVAL UPDATE UPSTAT is run from a PROGRAM (using EXECUTE DBMS) then it appears that the UPSTAT flag is still on on returning to the program. The program then prints a second set of rubbish update stats. EXAMPLE PROGRAM program execute dbms "include file 'C:\Program Files\SIR2002\stats2.pql'" end program ---stats2.pql--- RETRIEVAL UPDATE UPSTAT CASE IS 1 END CASE IS END RETRIEVAL c program noexecute c write "hello world" c end program ---Output--- End retrieval execution Database Update Summary Report ------------------------------ Database name: COMPANY Update level: 22 Date/time of update: 02/05/04 11:16:40 Journal file option: OFF Cases initially: 46 Cases added: 0 Cases updated: 0 Cases deleted: 0 Cases at end: 46 Records initially: 140 Records added: 0 Records updated: 0 Records deleted: 0 Records at end: 140 Record Previous New Updated Deleted Current Total Total --------------------------------------------------- --------------------------------------------------- Totals: 140 0 0 0 140 End of Update Summary Report End program execution Database Update Summary Report ------------------------------ Database name: COMPANY Update level: 0 Date/time of update: 02/05/04 11:16:40 Journal file option: OFF Cases initially: 1162690894 Cases added: 0 Cases updated: 1 Cases deleted: 1162690894 Cases at end: 0 Records initially: 2074980884 Records added: 673639132 Records updated: -221059919 Records deleted: -1546347280 Records at end: 0 Record Previous New Updated Deleted Current Total Total --------------------------------------------------- --------------------------------------------------- Totals: 22673639132XXXXXXXXXXXXXXXXXX 0 WORKAROUND Add a dummy program after the retrieval (in the included file/member) to force the upstat flag off. (ie uncomment the commented out section in the example program above.