CR 8 & Access 2000 - Errors about pdbbtrv.dll & recognizing file

[delu0007]

I just reinstalled CR 8 and am trying to open a report that is based on an Access 2000 database. The database that it was based on no longer exists, so I want to "Set Location" to another database. When I choose a database file, I get the following error:

Configuration Error.

Library "pdbbtrv.dll" cannot be opened. Please check its configuration.


This report was never based on this driver (BTrieve). After clicking ok to this error, I immediately receive another error:


Error recognizing file.

File "C:\{My database file here}.mdb" is not a known database type. Please choose again.


All the posts I've seen close to this error refer to CR 7 needing the new Access 2000 drivers. I have CR 8, and the versions of the dao drivers that I currently have are 8.0.0.4 (p2bdao.dll & p2ctdao) and 8.0.0.5 (pdirdao.dll).

If I try to create a new report, I get the same sequence of errors.

 

[FoxG]

Hi,

Try converting the database driver,and reselecting your Access 2000 driver from your list of available drivers

If this doesn't work try checking the properties for your ODBC link for Access 2000. Check that the default directory is correct.

Hth,
Geoff

 

[delu0007]

The reports are currently using the dao driver (PDBDAO.DLL). I tried using the "Convert database driver" menu option but it complains that the mdb file that I originally based the report on no longer exists, and I can't "Set Location" to a different file.

I'm not using ODBC, so I don't believe this applies.

The DAO dll is now named P2BDAO.DLL, but I don't know if that matters -- I can't change it anyway because of the error about the file not existing anymore.

 

[kenhamady]

The difference between PD and P2 is that P2 is the 32 bit driver and PD is the 16 bit. However, CR always refers to these drivers by there 16 bit name, even in 32 bit environments.

You say you reinstalled 8. Is the report originally a V8 report or another version? Did you upgrade? Can you create a new report using the Xtreme.MDB that comes with CR? Ken Hamady, On-site/Phone Crystal Reports Training/Consulting
Quick Reference Guide to using Crystal in VB

http://www.kenhamady.com/

 

[delu0007]

Most of the reports were originally created in CR 6 or 7, but they have all been saved in CR 8. I was working just fine with CR 8 until the middle of last week, when an error began popping up when trying to view the reports through a VB application (I had been viewing reports through the same VB app for quite some time with out any problems). The same reports would view correctly in the CR 8 Application. I tried registering some of the crystal dlls to try and fix the problem, but no luck. I figured the quickest fix would be to just reinstall CR 8. After reinstalling, the errors began to pop up withing CR 8 as well as in development mode.

I can create a report with the sample xtreme.mdb, which I believe is an Access 97 database. This would lead me to believe that there's a problem with my Access Drivers, but I will wait for another response to see if you have more help.

Thanks

 

[delu0007]

One more thing:

After trying to "Set Location" once and receiving the two errors I mentioned before, I try again and receive a password prompt for the access database (There is no password protection on the database). After clicking the cancel button, I receive the second error that I was getting previously about "Error recognizing file".

 

[kenhamady]

You can create a new report against Xtreme.mdb using DAO, but you can't create a new report against an MS Access 2000 MDB?

Do you have a version of MS Access installed on this PC? What version?

You say that these V8 reports were working from BOTH CR and VB up until that Wednesday, and then they started failing in VB but worked in CR? You Reinstalled CR and now they fail in CR as well?

Do you have v8 Developer?
What integration method are you using in the app?
Which version of CR provided the VB dlls that the app is using? Ken Hamady, On-site/Phone Crystal Reports Training/Consulting
Quick Reference Guide to using Crystal in VB

http://www.kenhamady.com/

 

[delu0007]

You can create a new report against Xtreme.mdb using DAO, but you can't create a new report against an MS Access 2000 MDB?
Yes, this is correct.

Do you have a version of MS Access installed on this PC? What version?
Yes, MS Access 2000 (9.0.4402 SR-1)

You say that these V8 reports were working from BOTH CR and VB up until that Wednesday, and then they started failing in VB but worked in CR? You Reinstalled CR and now they fail in CR as well?
Yes, this is correct.

Do you have v8 Developer?
What integration method are you using in the app?
Which version of CR provided the VB dlls that the app is using?
Yes, I have v8 Developer. I am using the 'Crystal Report Engine 8 Object Library' Reference from VB (Crystal Automation Server). The Crystal DLLs were provided with v8, the versions are: p2bdao.dll (8.0.0.4 12/7/99), p2ctdao.dll (8.0.0.4 12/7/99), and p2irdao.dll (8.0.0.5 12/7/99).

Since my last post ...

I also have a copy of Crystal Reports v8.5 upgrade that was still shrink-wrapped. I gave that a try this morning, but received the same errors. I then uninstalled all together and reinstalled v8 -- same errors still occurring.

Thanks for taking the time to help, I hope you can come up with a solution.

 

[kenhamady]

This is a strange one.

Did you install anything else that day to the PC that might have changed something?

Can you create a new simple MS Access 2000 database from scratch and see if you can create a new report against that?

When you are in CR, running a report against Xtreme sample data click:
help/about/more info

..to see that the dlls actually being used for MS Access are the ones that you think are being used. Do you have multiple versions of these dll's on the PC? Ken Hamady, On-site/Phone Crystal Reports Training/Consulting
Quick Reference Guide to using Crystal in VB

http://www.kenhamady.com/

 

[delu0007]

Did you install anything else that day to the PC that might have changed something?
Now that I think about it, I installed the scr8_distr_expert.exe which enables the 'Compiled Report' option for Crystal Reports 8(I was not planning on using this option for development use, it was only for a few personal reports). I would have installed it on Tuesday, October 2nd--I know reports worked immediately after that because I made a few that afternoon, I guess they may have stopped working after a reboot (but I'm not sure that I rebooted between Tuesday and Wednesday). On reinstall of CR8, that option is gone so I assume that it was all uninstalled.

Can you create a new simple MS Access 2000 database from scratch and see if you can create a new report against that?
I created a MS Access 2000 database with one table containing two fields and received the same errors I had been receiving.

When you are in CR, running a report against Xtreme sample data click:
help/about/more info

..to see that the dlls actually being used for MS Access are the ones that you think are being used. Do you have multiple versions of these dll's on the PC?
When I go to help/about/more info, there are multiple dlls listed. Two of those listed are p2bdao and p2irdao. Searching for these filenames and 'p2*' reveal no duplicate versions on my PC.

I reinstalled again this morning and made sure that all dlls beginning with 'p2' were removed during uninstall (They were).

 

[kenhamady]

Ok the straws I am grasping for are getting shorter.

I have the Distribution Expert installed, and Access 2000, and I have no problems connecting, so I doubt that was it. You didn't install or change anything else that day?

Can you check the registration of MDB files in windows explorer and make sure that they are still registered to MS Access? Have you tried reinstalling MS Access? Can you make an ODBC connection to Access 2000 from something other than CR?

Also, when you said:
>>I tried registering some of the crystal
>>dlls to try and fix the problem, but no
>>luck.

Which DLLs and how did you register them? Ken Hamady, On-site/Phone Crystal Reports Training/Consulting
Quick Reference Guide to using Crystal in VB

http://www.kenhamady.com/

 

[delu0007]

I don't beleive I installed anything else. I did a find for all files modified or created since last monday, and nothing unusual popped up. The Seagate Software folder (from reinstalling) and a Wise Installation Wizard folder (from the Distribution Expert) were the only new folders created.

MDB files are still registered to MS Access. No, I haven't tried reinstalling MS Acces (but I could try). I can create an ODBC connection to a MS Access database with the 'ODBC Data Source Administrator' -- and then use it to create a Crystal Report. I can also create a new report using the ADO 'Active Data Driver' and connecting to the same MS Access Databases.

When I said I tried to register the DLLs, I tried to use regsvr32 to register the p2*dao.dll files, but I got the error about 'entry point not found'. It's a familiar error, I believe it has something to do with the dll being self-registering.

---
My problems started while I was trying to use these reports to also work with SQL Server 2000 databases (I believe you were trying to help me solve that problem as well). The actual reports have not been modifed, and the problem when creating a new report would not be explained by this. Is there anyway that I could have messed something up from Visual Basic Code using LogOnServer or SetLogOnInfo in the Crystal Automation Server? I didn't think there was a way for me to make a permanent change to a dll or report from these routines.

 

[kenhamady]

Yes, the inability to create a new report against a new MDB means that there is a problem in the environment. Since CR works otherwise, and MS Access works otherwise the only thing unique to this problem would be the group of files used to make the connection. That would be the DAO driver. Reinstalling CR should have given you the correct driver, unless the registry for this dll file is messed up somehow and not getting fixed by the reinstall. I am not sure if the manual registration error is the problem, a symptom, or unrelated.

I am sorry, but I don't know where to take you from here. Ken Hamady, On-site/Phone Crystal Reports Training/Consulting
Quick Reference Guide to using Crystal in VB

http://www.kenhamady.com/