thread637-362741
Just a quick note for my own situation with this error. Using Access database and MAS90 4.0 ODBC driver. Linking was working until another PC on the LAN was linked. At that point, both PCs could see the database and link tables, but would kick back the error ProvideX odbc driver fileio table is not accessible when actually trying to open one of the tables.
Solution: after viewing a log file, it turned out the same name was used for the DSN, and the connection string from one PC was being remembered, rather than using the connection string supplied by the active PC. Creating unique DSN names in the DSN management console for each PC seems to have resolved this particular form of the error. There may be a similar issue at root for some of the issues I read in the linked thread.
Just a quick note for my own situation with this error. Using Access database and MAS90 4.0 ODBC driver. Linking was working until another PC on the LAN was linked. At that point, both PCs could see the database and link tables, but would kick back the error ProvideX odbc driver fileio table is not accessible when actually trying to open one of the tables.
Solution: after viewing a log file, it turned out the same name was used for the DSN, and the connection string from one PC was being remembered, rather than using the connection string supplied by the active PC. Creating unique DSN names in the DSN management console for each PC seems to have resolved this particular form of the error. There may be a similar issue at root for some of the issues I read in the linked thread.