Crystal Report 2008

0 views
Skip to first unread message

Ozella Vires

unread,
Aug 5, 2024, 10:26:09 AM8/5/24
to getugalatt
TerryCunningham and the Cunningham Group originated the software in 1984.[2] Crystal Services Inc. marketed the product[3] (originally called "Quik Reports") when they could not find a suitable commercial report writer for an accounting software they developed add-on products for, which was ACCPAC Plus for DOS (later acquired by Sage).[4] After producing versions 1.0 through 3.0, Crystal Services was acquired by Seagate Technology in 1994.[5] Crystal Services was combined with Holistic Systems to form the Information Management Group of Seagate Software, which later rebranded as Crystal Decisions and produced versions 4.0 through 9.0. Crystal Decisions was acquired in December 2003 by BusinessObjects, which produced versions 10, 11 (XI) and version 12 (2008).

The file extension for Crystal Reports' proprietary file format is .rpt. The design file can be saved without data, or with data for later viewing or sharing. Introduced with the release of Crystal Reports 2011 (version 14.0), the read-only .rptr file extension option allows for viewing, but cannot be modified once exported.[6]


Several other applications, including Microsoft Visual Studio versions 2003 through 2008, and Borland Delphi, at one time bundled an OEM version of Crystal Reports as a general purpose reporting tool.[7] Microsoft discontinued this practice and later released their own competing reporting tool, SQL Server Reporting Services (SSRS).[8][verification needed]


When you check the checkbox New Page After, you will see an icon just right to it. This icon represents Formula Workshop. Click this icon and type NOT OnLastRecord.


Some options you may be able to use are in the section expert are "Keep Together" which keeps all the lines of the section together, either on the current page (if there is room) or on the next (if not), or the "Suppress Blank Section". You could also try to shrink the height of the section, but this will probably not work in all cases.


In addition, to checking what other have mentioned above, after creating a new Blank Report, under Page Setup, the paper size for me was A4 by default. When I changed it to Letter, I would get a second blank page in the Print Preview as well as when physically printing to letter paper. Presumably this is due to going over the page boundaries. I was able to reduce the magins, and make the report content fit on the page.


need to create ssis package to run crystal report(s); I want to read a sql table and return values as parameters to cyrstal reports, and then email the report. Has anyone been able to do this? Thanks in advance for your help.


But if you have the Crystal libraries installed on the machine with SSIS, I would think you could use them in a Script task to do what you want to do.. It would be like building an app in VB to do it, only SSIS would be the container and not an EXEC..


There are some third-party utilities available which allow you to run a Crystal Report from the command line. So, once you have that working, your problem reduces to building the correct command line, with parameters in place, and then executing that from within SSIS - which isn't so hard.


The absence of evidence is not evidence of absence

- Martin Rees

The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response

- Phil Parkin


Thanks for all the replies...yes, I have thought about third party software to build command line; and I have not used Reporting Services at all yet. I think using vb script within ssis is what might work for me....Thanks again for all the help.


I was finally able to run a sssis package with variables passing to "Script Task" which in turns used Crystal Resources to genereate a pdf file. I had another task to email the pdf afterwards. Took some doing espically to copy the Crystal ddl files so ssis could add them as references. Also took some time to correct the login information and export options. I have some hard coded values....will have to tighten things up before production, but at least runs now on my pc....now see if I can redo this on my production box.


The first thing you have to do is copy the four crystal reports dll files into the sql server folder so they can be added in the ssis script reference; CrystalDecisions.CrystalReports.Engine.dll, CrystalDecisions.ReportSource.dll, CrystalDecisions.Shared.dll, CrystalDecisions.Windows.Forms.dll into C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies or your appropriate version folder.


A reference to 'C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies\crystaldecisions.crystalreports.engine.dll" count not be added.Please make sure that the tile is accessible,and that it is a valid assembly or COM component.


I copied the four crystal reports dll files into both "C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies" and "C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies" as that is what I have. I just checked my reference and it points to the folder "C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies", try that...


'A reference to 'C\Program Files\Microsoft SQL Server\90\SDK\Assemblies\ctystaldecisions.crystalreports.engine.dll' count not be added.Please made sure that the file is accessible, and that it is a valid assembly or COM component.


I am new to this SSIS. I need to create some .rtf file using Crystal report from the SSIS package. I saw the post that you already Used the ssis package to genrate a report using Crystal report. In my workplace, I am getting a new project where I have to do this with in a very short time. Our database server is SQl 2005. COuld yopu please help me by providing an SSIS package example and steps on how to do it. I would be so grate ful to you. Thanks in advance.


Off the top of my head here are a few of the ways

Crystal ADO to connect to the XML files generated by the system for BAQ reports

Crystal ODBC - set up ODBC DSNs on each local system for custom reports that connect directly to the database

Or you might be able to embed credentials right inside the Crystal report

And in E10 - you might be able to use Company Maintenance - Email and Reporting - the fields for the ODBC connection?


In dealing with a recent post about an upgrade to Crystal XI R2 mixing badly with an old VS 2003 project ( ), I've been attempting a few things to get past the issues with missing parameters and so on. I found that I actually was using a parameter in the report I was trying to run, so I assigned the proper value to said parameter, ran the report, and lo and behold all was well. The data was coming back correctly, no errors, everything seemed fine.






Then I checked the results against the production environment of this application, hosted on a remote server, and was disappointed to find that the reports were now coming back blank. After some deeper investigation, it turned out that the data it was retrieving was coming from my development server and not the production server like it had in the past. As far as I can tell, it is completely ignoring the dataset that I'm assigning to the report object (which is filling with the correct data) and just running the query built into the report, which is connected via ODBC to my development server database. I have no idea what this is going to do when the application is run from the production environment itself, as in, my customers running the application from their desktops, and I have no way of testing this.






I will fully admit that the report may be poorly designed, because then and surely enough now I'm no crystal expert, but as I said in my previous thread, this all worked fine until I upgraded to XI R2 for another project. Essentially what I want is for the report to accept the dataset and display ONLY that data, and not run a query against the ODBC connection. Is there some way to force this behavior? Here's a sample of my code, if it helps:






I've tried to reassign the report's connection to the currently connected database (code snippet below) but every time I end up getting a logon failed error message, even when I know for sure the login data is correct, and even when I'm just connecting to my local development server.






I ran that after loading the report, but received a failed login error every time. Any suggestions on how to proceed with this? I'm at a loss because up until now I've never had a problem like this with a crystal report, they always just took the datasets I gave them without ever running anything else.


Renamed the datasource and tried it again, this time it crashed with a Logon Failed error. I uncommented the logoninfo code I linked earlier and got the same thing. It seems to still be trying to use the original ODBC, and because it can't find it it throws logon failed.


Ok. Now I want you to go over [this =/pub/wlg/13270] [original link is broken] [original link is broken] [original link is broken]; blog. It takes you through troubleshooting issues with datasets and Crystal Reports. The fact that you get db logon request, tells me that there is something wrong with the dataset (or the report does not understand it). Thus, if the original datasource is available the report connects to it once it fails with the dataset.


After attempting quite a few of the proposed solutions, nothing seemed to be working. Due to the limited usage and number of reports in my application, I decided to try recreating them from scratch (there are only 3 and 2 are nearly identical) using only the crystal 9 integrated designer in VS2003. My initial testing has been successful, even using the same base query that the failing reports were using.


Dropping everything and recreating all of ones reports is not the greatest solution, but at worst it's a few hours of tweaking, as opposed to days of frustration messing around trying to get the "corrupted" reports to work again. Thank you again for your assistance.

3a8082e126
Reply all
Reply to author
Forward
0 new messages