Personalization, Customization and Productivity Tools

[zalmi]

As an aside. I tried a simple Pass-Through just accessing IM1_Masterfile and trying to get the im number and description. I got this error: [ProvideX][ODBC Driver][FILEIO] Table is not accessible (#12)

[BigLouie]

Can you paste in your SQL statement?  Did you use Crystal to generate it as suggested.

[connex]

Open the ODBC Administrator control panel and check the driver for the MS Access Database Driver. 

If the driver is listed as Microsoft Access Driver (*.mdb, *.accdb) then the 2007 or 2010 driver is loaded.  If the driver is listed as Microsoft Access Driver (*.mdb) then a prior version is loaded. 

It is possible to have both loaded at the same time and you should be able to select the one without *.accdb support.

[zalmi]

This is what the simple one looks like

SELECT IM1_InventoryMasterfile.ItemNumber, IM1_InventoryMasterfile.ItemDescription
FROM IM1_InventoryMasterfile;

and this is in the properties

ODBC;DSN=SOTAMAS90;UID=zb;COMPANY=DON;PWD=xxxxx;Directory=\\DX-Server\Sage\MAS 90\MAS90\;CacheSize=4;StripTrailingSpaces=1;SERVER=NotTheServer

As I said it worked perfectly till last week. We upgraded to 4.3 in January and these reports were run 4-5 times a day

Thanks for your help.

[zalmi]

connex. I checked one workstation and all it has is mdb.

[zalmi]

BL

You suggesting that Crystal should generate the pass-through querry and not Access?

[zalmi]

Still playing with this. All my queries from Access run fine. When I open CrystalI check the databse location and verify the data base and then I get this message....

1. Failed to open a rowset

2. Query Engin Error: 'DAO Error Code:0xc4a

    Source : DAO.Database

    Description: ODBC--call Failed'

And this is after thequery in axxess runs fine and database is verified

[BigLouie]

Normally I suggest that the user open a new Crystal report and use the one table. Then pull the fields you want into the detail section. Next go to the Show SQL Statement and copy the statement and paste it into the Access Query. The Crystal SQL statement is always correct.

[BigLouie]

This:

ODBC;DSN=SOTAMAS90;UID=zb;COMPANY=DON;PWD=xxxxx;Di rectory=\\DX-Server\Sage\MAS 90\MAS90\;CacheSize=4;StripTrailingSpaces=1;SERVER =NotTheServer

Should be this:

ODBC;DSN=SOTAMAS90;UID=zb|DON;PWD=xxxxx;Di rectory=\\DX-Server\Sage\MAS 90\MAS90\;SERVER=NotTheServer

[thebottomline]

BL,

As recommended by  Alnoor, this is the one I have been using with much success:

ODBC;DSN=sotamas90;UID=jas|btc;PWD=XXXX;Directory=\\ServerName\Apps\Sage\MAS\v440\MAS90\;EnforceDouble=1;StripTrailingSpaces=1;SILENT=1;SERVER=NotTheServer

If you don't strip out the trailing spaces, you are going to get a lot of hidden garbage in your string fields which can have negative consequences if you are using that field in a bar code printing program and fail to strip the spaces then.