Scenario:
> SQL6.5 DB backend for client/server application;
> all users login to the app which connects to the DB via ODBC through a generic userID;
> therefore no destinction is possible in the activity window for different users;
Problem:
> some users experience random lockups and/or fatal errors on their workstations when running reports or batch jobs, where the error message claims that table and/or cell data is missing, however external queries show that data is there and available;
> vendor claims these are DB problems and not bugs;
Question:
Is it possible to construct a SQL and/or trace command which could catch the offending SQL statement?
> SQL6.5 DB backend for client/server application;
> all users login to the app which connects to the DB via ODBC through a generic userID;
> therefore no destinction is possible in the activity window for different users;
Problem:
> some users experience random lockups and/or fatal errors on their workstations when running reports or batch jobs, where the error message claims that table and/or cell data is missing, however external queries show that data is there and available;
> vendor claims these are DB problems and not bugs;
Question:
Is it possible to construct a SQL and/or trace command which could catch the offending SQL statement?
