Crystal Reports: Database Error

[acerocks]

I get the following message on an XP pro machine with Service pack 2 using Crystal v8.5.

Crystal Reports: Database Error

Error opening file.
File could not be found: " xxxxx ", at locations: " xxxxx"

(Note ‘xxxxx’ it’s the name of the table I am trying to use in the report)

The above seems to have just popped up once XP SP2 went on. I am trying to access a MS Access database with Crystal v8.5. With in the database I have several Access tables and a few ODBC linked tables to other data sources. I can see the ODBC linked table’s fine but not the Access tables.

Any idea?

 

[hneal98]

Did you try setting the location? Also, you might want to check the Show Query Dialog to make sure the alias is correct all through the query.

 

[acerocks]

As you suggested, I did all 'standard' checking for THIS and THAT prior to posting the HELP ME message! To get a bit more detailed, the error message is with any Access database table I try to use on a Crystal report. Even if I create a new blank report using the standard 'Northwind.mdb" sample that Microsoft ships I get the message as soon as I add a table to the report.

Now if I setup an ODBC DSN and point to the same exact tables that cause the error as I mentioned above. I have no problem. But I can't use an ODBC link to the Access Table as a solution.

This seems to only have started happening once XP SP2 was updated on the computer. So I can only believe that the problem is with something MS DAO related.

 

[fredp1]

If you think its a DAO problem try getting the microsft MDAC update. Also I believe there is a service pack for the Jet engine (could be SP8) that is not with MDAC.

If you are still having problems... specify the version of Access that your using and what tests you have already done.
Also have you tried SP3 for Crystal?

Ive tried Win XP SP2 and Access 2003 and 8.5 sp3 and its okay for me.

Cheers
Fred

 

[acerocks]

I have a matched setup to that of you excepts for the 8.5 SP3.

I will try that now and then report back the results.

 

[acerocks]

Well that didn't fix the problem but... I did fix the problem.

The access database is MS Access 2000 format. I converted the database to Access 97 Format and everything worked instantly. I also did another test and converted the database to Access 2002 and again instantly everything worked fine.

Go figure

 

[hneal98]

good for you.