<< My code was using a view to combine three very active tables to test for existence of data (including a where limit = 1), and then enable or disable a button that could create a full report. I rewrote the code to do a direct look at the one table that was really necessary, and eliminated the view from the "test for any data" code. The same view is always successful when used to create a report, but would fail during the busiest times of activity. I could never get it to crash in single user tests, or in limited 9.1 testing before the rollout. Problems only appeared when the database (these particular tables) were very busy in live operations. >>
Thanks, this is very helpful. -- Larry
