I think there is a new Driver that you need.
The link to the update has been posted here recently. If you keyword search you should find it. Ken Hamady
If I create a new report I can connect to Access 2000, no problem. But if I try to change the Database for an existing report from the old db to the converted one I still get an error ... ??? Can someone please open my eyes ?
That is a completely different type of problem. You need to identify what these reports (the ones that fail) have in common.
Are you running them from the design environment when they fail or from an App?
Check for which tables are used, and how they are joined.
Also check for subreports.
It is also possible that they use a User Defined function, and this function's dll isn't available on the new PC. This function would be in a formula. Are there any formulas that these reports have in common that aren't on the others?
Got it. It wasn't a CR thing at all. The converted database was a little bit screwed up (only one table). All reports that access this table came up with the error. Now everything is OK.
Thanks a lot, 'cause you put me in the right direction !
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.