B
buzz
I am running Microsoft Access 2002 as a front end to view reports from a IBM
DB2 database. This DB2 database can get very big and depending on a query
ran, the query can take some time to process as for all the records it has to
search through. I have been checking with my DBAs to get the DB2 database
optimized. When using the DB2 tools/client software, an SQL query through it
will return records after a decent amount of time (a few minutes) but if the
same query is run within access, it appears to get an ODBC call failure which
I am believing it to be a timeout. I have found within Access an OLE/DDE
timeout setting but can only max it out 300 seconds and I still get the ODBC
timeout. Is there anything else I can do to allow my queries to complete??
Are there ways to get around the timeout?? Are there newer versions of
access that won't timeout?? What can I do??
DB2 database. This DB2 database can get very big and depending on a query
ran, the query can take some time to process as for all the records it has to
search through. I have been checking with my DBAs to get the DB2 database
optimized. When using the DB2 tools/client software, an SQL query through it
will return records after a decent amount of time (a few minutes) but if the
same query is run within access, it appears to get an ODBC call failure which
I am believing it to be a timeout. I have found within Access an OLE/DDE
timeout setting but can only max it out 300 seconds and I still get the ODBC
timeout. Is there anything else I can do to allow my queries to complete??
Are there ways to get around the timeout?? Are there newer versions of
access that won't timeout?? What can I do??