Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. dward10

    ODBC Errors When Linking Tables From Access to DB2

    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
  2. dward10

    ODBC Errors When Linking Tables From Access to DB2

    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...
  3. dward10

    ODBC Errors When Linking Tables From Access to DB2

    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...
  4. dward10

    ODBC Errors When Linking Tables From Access to DB2

    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...
  5. dward10

    ODBC Errors When Linking Tables From Access to DB2

    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...

Part and Inventory Search

Back
Top