You could try changing the name of the table while doing this operation. Also you could set a flag in a table that would be tested before the report is run. If the flag is set to say "No reports allowed" then your program could issue a warning and ask the users if they want to wait or go do something else.
I'm not quite sure how to handle the potential situation where a user is running the report and your download system starts up. I suppose you could set and test for a flag that says "Report running" in the same way as the "No reports allowed" flag. ======================================== At 11:24 PM 11/25/2001 -0500, you wrote: >Hello all, > >I have an R:base command file that runs automatically every hour (many >thanks to Ian Stone for his utility). This command file downloads data via >ODBC to a table and then performs some R:Base wizardry for about 5 minutes. > The problem is - i have users who access this table to print a report, >sometimes unknowingly while this command file is running. Obvoiusly, when >the command file is running the data is changing frequently. i would like >to prohibit access to this table while the command file is running. tried >"SET LOCK tablename ON" but other users still can print report. I guess >this just means it locks out writes to the table. Is there a command I'm >missing to temporarily suspend read of the table? There are no passwords >on this database. > >Thanks >
