Sage 100

 View Only
  • 1.  ODBC-Call Failed [Providex][ODBC Driver][FILEIO]Ta

    Posted 09-18-2013 14:25
    ODBC-Call Failed [Providex][ODBC Driver][FILEIO]Table is not accessible (#12) Customer had an Access 2003 SP3 database connecting to Sage 100 ERP v4.5. We did this via linked tables using ODBC. For some reason the connection stopped working with the error ODBC-Call Failed [Providex][ODBC Driver][FILEIO]Table is not accessible (#12) I could connect to ODBC via Crystal and pull data. I could connect to ODBC and import a table to Access I just could not link a table without getting the above message. Resolution was to go into ODBC for SOTAMAS90 and change the paths for all Sage files to be UNC vs drive letter. Once I did that it worked just fine.


  • 2.  RE: ODBC-Call Failed [Providex][ODBC Driver][FILEIO]Ta

    Posted 09-18-2013 16:55
    Customer called back - issue returned. I'll have to roll up my sleeves and look at it again tomorrow. I'm more suspicious that there's some strange interaction with MS Access and the ODBC driver (and possibly the network).


  • 3.  RE: ODBC-Call Failed [Providex][ODBC Driver][FILEIO]Ta

    Posted 09-19-2013 00:03
    I like to use PTQ's instead of linked tables. Don't seem to have as many issues.


  • 4.  RE: ODBC-Call Failed [Providex][ODBC Driver][FILEIO]Ta

    Posted 09-19-2013 09:40
    Any chance they have another version of mas running on the desktop?


  • 5.  RE: ODBC-Call Failed [Providex][ODBC Driver][FILEIO]Ta

    Posted 09-19-2013 09:44
    Logged back in today. Took me a little time to remember what I'd done originally. From what I can see I did in fact use PTQ. The linked tables seem to be there just as part of an original design idea but I don't think they're used. The PTQ were pointing to another server which had been ""decommissioned"". I also had some luck creating a new ODBC DSN and using the database link maintenance to align each table with the new DSN.