Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error 20534 Error Detected by Database DLL

Status
Not open for further replies.

tpbjr

MIS
Oct 8, 2004
120
US
Hi all,

I just want to say thank you very much for getting me this far. I have completed all aspects of my code changes from DAO to ADO. Unfortunately, my crystal reports are causing an error when I try to print or preview them on the screen.
It works fine on my developement machine but on a clean machine I get the error 20534. I am using the VB 6.0 and Crystal Reports that came with it (version 4.6).

Any help in the right direction would be deeply appreciated. This is like that last bolt when trying to get your tire off. :)



Thank you for all your help

Tom
 
Attempting take part in my own question. My original problem with my app was that it was using DAO and did not work on users computers who did not have MS Access 97 installed. Everyone at TEK-TIPS was suggesting to convert my logic from DAO to ADO and I did. Now the application works on a clean Windows XP machine but the report portion does not. It looks like from the Crystal Reports help looking at required files such as P2BDDAO.DLL, P2CTDAO.DLL and P2IRDAO.DLL, I still have a DAO problem. I am thinking that since it works on developement machine that I have DAO for Access setup correctly but I cannot get my install program to setup a clean machine correctly for DAO so the reports can work. Any ideas to my thoughts? Am I way off base? Any help toward a solution would be great.

Thank you for all your help

Tom
 
Ok--I am feeling sick and lonely:)
I am answering my own questions in hopes someone can give some input.

After more research I have concluded the following:
CRW version 4.6 is only DAO compliant. Now, since I have upgrade my VB code to ADO and MS Access version 97 database (back end). It looks to me like CRW 4.6 is not going to work unless I purchase the MS Access 97 Runtime library so I can distribute it with my application? Does that sound about right? If I am correct, does anyone know a link to get to see what this damage is going to cost me?
I am just a weekend programmaer--I cannot afford big bucks for this road block!

Thanks again.

Thank you for all your help

Tom
 
Can't you just download MDAC 2.8 for free? It's on Microsoft's web site. That should be the runtime libraries that you need to have installed on client's machines.

-David
2006 Microsoft Valued Professional (MVP)
 
I thought I had tried that before and had some issues. I just tried it again on a clean Windows XP machine as Administrator and it said, "Fatal Setup Error", Setup not allowed on this operating system.

I cannot prove it because I do not have the Access 97 distribution kit but I do not think you can distribute access runtime stuff unless you have a developers license.

Anyone know where I can get that real cheap since it is old stuff anyway?

Thank you for all your help

Tom
 
>Everyone at TEK-TIPS was suggesting to convert my logic from DAO to ADO

Everyone? Only one, as far as I can see (and to be fair you hadn't mentioned Crystal Reports at that stage)

>Can't you just download MDAC 2.8 for free?
>I thought I had tried that before and had some issues

You also need the correct Jet updates (and possibly ODBC components, depending on your target OS), which haven't been included in MDAC since version 2.5. They are, however, available seperately. Here's some technical info and the necessary links for various operating systems:
 
So does everyone think that Crystal Reports 4.6 is compatible with the new JET and MDAC? I know I am asking for help and I will keep attempting any suggestions, god knows I need all I can get but I think it is this darn old version of CRW that needs the DAO3.5 run time stuff. I wish I new a way to get that on a client machine with my installation package. I was reading something from the Crystal site about DAO3.5 being required.

That is why I am think if I had the Access 97 distribution kit, I could legally include them in my installation and everything would register correctly.

I will try the JET update as well. Thank you so much for your input. I will let everyone know the results. Thanks again, everyone.

Thank you for all your help

Tom
 
That did not work. I even tried to install the MDAC 2.8 again after installing the JET 4 and I got the same error message, "The setup does not support installing on this operating system".

I honestly believe that if I can get the DAO350.DLL and its dependency files installed properly on the clean XP machine that I have, then it will work. I have tried to copy the DAO350.DLL into C:\Program Files\Common Files\Microsoft Shared\DAO on the new machine just like it is on my development machine. Then I registered it but it still does not work. I know sure enough if I install Access 97 or later on the clean machine the this whole problem is going to go away but I cannot depend on customers having Access 97 or older. :(

I am facing a brick wall and cannot even turn around at this point. HELP:)

Thank you for all your help

Tom
 
Ok, everyone, you are all going to think I am crazy but I just copied the DAO350.DLL and registered it and now the reports are working. I hope this helps anyone else with this issue. When I had tried that approach before it was when my entire application was using DAO instead of ADO.

Now, it looks like I have to flat the computer all over again because I do not know if it was as simple as including the DAO350.DLL in my installation or a combination of install the JET 4 and manually copying the DAO350.DLL.

I guess the only way I will know is to flat'n the computer and try to register the DAO350.DLL and see if that fixes it, if not take the next step, and so on.

I really want to thank everyone for working through this with me and if you still have any suggestion, as always I would appreciate it very much.

Thank you for all your help

Tom
 
I thought I would let everyone know that it worked.

To resolve my error 20534 issue I started with new install of Windows XP. In my install program I included DAO350.DLL in my install package and selected for it to be self registering. Next I included the JET35SP3.EXE file to be copied to the applications default directory.

I tried to preview a report and it popped up with a user id and password dialog box. I closed it and executed the JET35SP3.EXE file. It installed the jet components then I tried to print again. YES, YES, YES, it worked.

I hope this information helps someone else who has had the same issue with CRW 4.6.




Thank you for all your help

Tom
 
Not to keep draggin this out but I wanted to let everyone know what else I did. I reinstalled Windows XP again but this time I did not have to run the JET35SP3.EXE.

Instead, I included MSJET35.DLL (Windows\system32 folder) and the DAO350.DLL (Share folder) in my install. Wah-la, everything works great.

Thanks again everyone.

Thank you for all your help

Tom
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top