Search results for query: *

Phazoo You get the FileIO error coz the ASP script is unable to access the MAS90 tables/file (whatever the hell it is stored as). This happens because when you use ASP, it accesses the MAS90 directory using the permission set by IIS and this userid does not have access to the MAS90 directory...

OK - Here's the thing with the FileIO Error - IIS tries to access the directory/drive to get to the MAS90 files. However it does not have permissions to it - and therefore fails. What you need to do is to first create a userid/password in the Administrative Tasks -> User Management. Then go...

I have an answer to your question here - Look into the access permission of the directory where the MAS90 files reside. U will need to grant the IUSR_XXX permissions on the said directory. Doing this will solve your current problem but might bring in new problems as in my case. I now get ...

Kieth Your answer led me to think a little today and I checked permissions of the IUSR on the MAS90 directory and Bingo - it did not have permissions to the directory. Anyway - that problem was fixed only to be replaced by another as follows - Provider error '8000ffff' Catastrophic failure...

In my case the server running the MAS90 is also the web server running IIS. So access is not the issue. I can access the MAS90 files on the server from the server or elsewhere using the MAS 90 32-bit ODBC driver. I dunno why the ASP code doesn't see the tables. Do I have to qualify the...

Hi I get the same error - Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [ProvideX][ODBC Driver][FILEIO]Table is not accessible. Help :-(

Hi Did anyone find a solution to this problem. Would be much obliged if someone could post the fix. Thanks Ritesh

Hi Again I also tried using the Providex 3.22 driver. This is confusing, there are two drivers - a client and a server. I installed the client driver on my machine and tried to import data into excel which I could earlier using the MAS90 32 bit driver. But with the new Providex driver, it...

Hi This thread has been helpful in my connecting to the MAS90 server using ASP. I am using the MAS 90 32-bit ODBC driver. The connect command does not complaint, but whenever I issue a simple select on any table for example 'Select * from IM1_INVENTORYMASTERFILE ' or sililar I get the following...

Hi I am getting the same error. The connection is fine since it doesn't report and error. However any query I give comes back with table not found. I have no idea on what to do. Any help will be greatly appreciated. Thanks Ritesh