I set it to No commit and still get the same response. The thing about this problem is, sometimes it will go through without a hitch and others it gives me the error every time I try.
Thanks again
Danny
I am not able to find what sql is causing the interrupt. I can tell you that it is a select query that uses date/time criteria to filter data. Off of that sql is another that sums the results and one other that averages them. The table it is retrieving information from has over 300,000 rows...
I am linking tables to a db2 database in ms access. When running queries and reports, I often receive the following error: "ODBC--Call Failed" ... "SQL0952N processing was cancelled due to an interrupt. SQLSTATE = 57014 (#-952)"
It seems that this is likely caused by the isolation level...
I am linking tables to a db2 database in ms access. When running queries and reports, I often receive the following error: "ODBC--Call Failed" ... "SQL0952N processing was cancelled due to an interrupt. SQLSTATE = 57014 (#-952)"
It seems that this is likely caused by the isolation level...
I am linking tables to a db2 database in ms access. When running queries and reports, I often receive the following error: "ODBC--Call Failed" ... "SQL0952N processing was cancelled due to an interrupt. SQLSTATE = 57014 (#-952)"
It seems that this is likely caused by the isolation level...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.