I was told on a newsgroup to include
Crystal_Database_Access2003.msm
Crystal_Database_Access_enu.msm
Crystal_regwiz2003.msm (on this one in Properties tab Merge Module prop.
SetLicenceKey to product key code that you get from Crystal.)
I thought it was a real pain and, maybe not entirely necessary and added a
huge foot print to my distribution. So, there is a .NET Resource Kit that
you can download for free on the internet. It is full of tons of free stuff
and code.
One of those items is a Component One reporting control that works great for
me. I have had some trouble print previewing--but maybe they have that
fixed by now.. It's foot print is very minimal.
HTH
Shane
"Atley" <at*****@homtmail.com> wrote in message
news:%2***************@tk2msftngp13.phx.gbl...
How do I "stick in the product code and include a lot of CR libraries" ?
I am not sure of what you are saying...
Also what is this "Component One that you are talking about?"
"SStory" <Th*******@TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:u4**************@TK2MSFTNGP12.phx.gbl... seems you must stick in the product code and include a lot of CR
libraries. Was a real pain for me so I switched to a simpler Component One report
tool with the .NET Resource Kit--free...
"Atley" <at*****@homtmail.com> wrote in message
news:ud****************@TK2MSFTNGP12.phx.gbl... I have installed an application that I created and everything works except the Crystal Reports components... I check, they are in the Setup
Files, but it seems like the dependancies are not all there...
What can I do to force these dependancies to install?
