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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Crystal Report problem on TARGET machines.

Status
Not open for further replies.

Bojangles

Programmer
May 27, 2000
32
Hello.&nbsp;&nbsp;I am trying to get mailing labels to print in a VB6 application that I wrote. I've hit a wall both ways I've tried.<br><br>1 - I have used DataReport Designer to succesfully create regular reports, but see no way to conveniently create mailing labels (which I must have).<br><br>2 - I have also used Crystal Reports which allowed me to very easily create regular reports AND mailing labels.&nbsp;&nbsp;But I've been unable to get my Crystal Reports to Show on TARGET computers.&nbsp;&nbsp;I have spent 3 months wrestling with that.&nbsp;&nbsp;I have put all Crystall Dlls in my developer machine's System directory which helped eliminate some of the registering problems.<br>Now in Setup on a client machine, I do get the message that msado21.tlb could not be registered.&nbsp;&nbsp;I do not know how to correct that, so I ignore.&nbsp;&nbsp;Then when I execute the program, all goes well, except when a Crystal Report is supposed to show,&nbsp;&nbsp;I get an error... ERROR DETECTED BY DATABASE DLL.&nbsp;&nbsp;I really don't know if the msado21.tlb is causing the problem or something else is.&nbsp;&nbsp;I am using ADO, and am developing on a machine using Windows 2000.<br><br>If you can help me with #1 or #2, I would be greatful.<br>Thanks,<br>Bojangles <br>
 
Have you tried Crystal Report web site and look for <br>your problem in the knowledge base or FAQ section?<br><br>You can also log in your problem using the on-line<br>form of the site.
 
Hi Bojangles,<br><br>My friend, If you are trying to deploy your application on Windows 95 then you have required some additional step before start installation of your application. If this is not a case your target machine is same as your development machine then before installation of your application run MDAC_TYP.EXE on target machine and&nbsp;&nbsp;then start your application installation and check. <br>If it works please give me&nbsp;&nbsp;credit for this because I had spend lot of time in this to find out the way to resolve this type of problem. I had gone with this type of problem but for Windows 95 and windows 98 and NT not for Windows 2000.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top