Seagate Crystal Reports Version 8 Download
Tacio Allaire
The report is not loading on my asp page. Connection to DB is correct no errors where thrown. I used to install my app in a win server 2003 sp2 but now I migrated to win server 2008 sp2 and the reports are not showing anymore. Any ideas or links on how to install seagate crystal reports 8 on win server 2008?
Crystal Reports is a business intelligence application used to design and generate reports from a wide range of data sources. Several other applications, such as Microsoft Visual Studio, bundle an OEM version of Crystal Reports as a general purpose reporting tool.[1] Crystal Reports became the de facto standard report writer when Microsoft released it with Visual Studio
I am using Crystal reports Version 8 and frequently get the error 'Seagate Crystal Reports: Database Error' when I try to open a previously working crystal report file. The error occurs when I click on the Database menu. Every time I get this error I end up redesigning the report as the I have not yet found a solution and I cant run the report.
Ken Hamady
Crystal Reports Training and a
Quick Reference Guide to VB/Crystal RE: Seagate Crystal error ehawkins (IS/IT--Management)(OP)12 Feb 01 13:36We are running Crystal 7 inside a 32 bit application called ReMACS (Accounting software for fast food restaurants). ReMACS was developed in Delphi 3 and we are using Delphi VCL to embed the Crystal reporting engine into ReMACS. If we run ReMACS stand alone Crystal reporting engine has always worked like a champ. We are now testing running ReMACS ASP with the hosting by Window 2000 Adv Server and Terminal Server client for the remote connection. ReMACS works great but Crystal return the error and locks up the connection.
Thanks for your first response
Ed Hawkins
ehaw...@vom.com RE: Seagate Crystal error kenhamady (Instructor)12 Feb 01 17:18There are too many layers here for me to sort it out. My guess is that the ODBC connection (for CR) needs to be local, and isn't working remotely. As a test, does a report with saved data run OK? This will help you determine if it is the report engine or the database connection that is choking. Ken Hamady
Crystal Reports Training and a
Quick Reference Guide to VB/Crystal RE: Seagate Crystal error ehawkins (IS/IT--Management)(OP)13 Feb 01 16:51Ken,
We tried running a report with the data save in the report and got the same error say pdsodbc.dll not found. I also tested running the report on the Win2000 Server ( no terminal server ) got the same error.
I would appreciate you advise
Ed Hawkins RE: Seagate Crystal error kenhamady (Instructor)13 Feb 01 18:47>>If we run ReMACS stand alone Crystal >>reporting engine has always worked like a >>champ
So this isn't true when run on Win2K Server standalone? Is the ODBC configured correctly on the server? Is this DLL on that box and registered correctly? Ken Hamady
Crystal Reports Training and a
Quick Reference Guide to VB/Crystal RE: Seagate Crystal error ehawkins (IS/IT--Management)(OP)13 Feb 01 21:19Ken,
Remacs printing out Crystal has always run like a champ on NT4
We have been using NT4 servers as workstartions in Taco Bells and are now testing it with Win2k Advanced Server.
We have yet to get past the Crystal error on Win2K server.
We have tried running Remacs thru Win2k Terminal Server
Then running Remacs directly on the Win2k server using the server as a workstartion. Same problem in both situations.
I have configured the odbc DSN 100s of times for Remacs in NT4 and Win2k Advanced. Should I be looking in Crystal for some odbc settings. Remacs runs great as an ASP using terminal server. Better than standalone in the restaurants so we are anxious to get past the crystal error.
Thanks again for your time RE: Seagate Crystal error kenhamady (Instructor)14 Feb 01 08:03Nothing obvious jumps out at me.
This error may not have to do with the DLL itself. It will actually be P2Sodbc if you are using 323 bit Crystal, but they generate the same error.
I assume that you have confirmed that the P2sodbc.dll is in place and registered? Ken Hamady
Crystal Reports Training and a
Quick Reference Guide to VB/Crystal RE: Seagate Crystal error PDog (IS/IT--Management)20 Nov 01 23:50I'm having the same problem. OEM version of Crystal reports 6 running on Windows 2000 Adv Serv running terminal services. Checked the Seagate Software site for a fix - no luck. Applied all the service packs and updates from Microsoft. No fix.
I'll check with the OEM tomorrow.
Paul RE: Seagate Crystal error PDog (IS/IT--Management)25 Nov 01 03:42Fixed the problem. Here is the tip:
>> Copy all the .DLL files from the CRYSTAL directory to the
>> SYSTEM32 directory.
>>
>> CORRECTION STEPS:
>>
>> 1. Open Windows Explorer and locate the \\CRYSTAL directory.
>>
>> 2. Select and copy all the .DLL files to the \WINNT\SYSTEM32
>> directory.
It worked for me!
hth,
PDog googletag.cmd.push(function() googletag.display('div-gpt-ad-1406030581151-2'); ); Red Flag This PostPlease let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.
CancelRed Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.
- What are the Product End of Life Dates for older versions of the Crystal Product Suite?
- When was the end of life date for Crystal Info, and Crystal Analysis, and Crystal Enterprise?
- When the supported ended for older versions of Crystal Reports?
Crystal Reports Report Enterprise Server Seagate Info Analysis Holos Legacy EOL tech support crystalcare crystal care case case message ticket issue bug error migrate migration upgrade , KBA , BI-RA , Reporting, analysis, and dashboards , BI-BIP , Business intelligence platform , BI-DEV , Business Intelligence Software Development Kits (SDKs) , How To
Accpac (now Sage 300 ERP) was originally developed by the Basic Software Group in the eighties in Vancouver. They started a project to have a new WYSIWYG report writer as part of the product rather than the codes based approach being used. This project was cancelled and some of the people involved quit and started their own company to develop Crystal Reports (then Quick Reports). This was originally developed as an add-in product for the MS-DOS based Accpac Plus. Then they generalized the product to dynamically look at any database and that became the Crystal Reports of today. The original founders then struck it rich when they sold their company to Seagate in 1994, which was trying to branch out from hard disks to software. Eventually Seagate gave up on this and Crystal went private and independent as Crystal Decisions. Shortly after in 2003 it was sold again to Business Objects. Then in 2008 Business Objects was bought by SAP where it lives today.
All of Sage 100, 300, 500 and X3 ERP use Crystal Reports as their main reporting engine. Sage HRMS and Sage CRM also use Crystal. We all adopted Crystal long ago at some stage or another. Sage 300 ERP adopted Crystal when we switched from using CARET (the Computer Associates report writer) back at version 3.0A.
Crystal X and XI then followed and these worked very similarly to Crystal 9. Another nice thing was at this point Crystal had adopted an extensible file format, so the file format stopped changing between versions making upgrades easier.
Crystal has now released Crystal Reports 2011 and this fixes most of the problem in CR 2008. So we should start to see ERP packages moving forwards again. This version still only supports .Net and Java interfaces but has fixed a number of bugs and deficiencies that were causing adoption problems.
Sage ERP 500 (previously MAS 500) tries to simplify report customization by actually generating reports based on a higher level report designer built into the Sage ERP 500 product. This then eliminates a lot of the challenges in customizing reports inside the Crystal Designer. However this means that Sage ERP 500 uses the Crystal Design API and this API changes a lot from version to version making upgrades much harder. Sage ERP 500 also controls access to its database via a customer ODBC driver that then adds the Sage ERP 500 security model to the generic ODBC access.
Comprehensive. Filled in a couple of gaps in my Crystal knowledge. First time I used early Crystal version, took so long to run a report I kept cntrl-alt-deleting. Third time, I left my laptop alone to nip out for a sandwich. Came back, to a beatifully formated report. Thereafter about the same product embedding experiences. Except for one. We had a shocking time with dll hell. Ironically our Crystal account managers, name was Sue Yu (guess what my product marketing kept suggesting). Well we ended up with free tix to Crystal Dev Conference on the Vancouver water frount. Seattle let loose a 6.x earth quake. That shook things up and got the dialog going back to positive.
Crystal Reports has been around for a long time. Some might say too long. Over its 19 year history its certainly become very widespread, and I have nothing bad to say about its presentation. But 19 years of evolution and attempts at backwards compatibility can play havoc with an object model. A case in point: If you want to attach a reports to a different database at run time - a pretty common occurrence - you have to write surprisingly unlikely code. Its easy enough once you know how to do it, but why isn't there any centralised connection information?
Crystal Reports has also changed hands a lot over the years, from being owned by Crystal Services, then Seagate, then Crystal Decisions, then Symantec, then Business Objects and finally SAP. This led to a plethora of different version names, and to make things more complicated, the versions that were bundled with Visual Studio were separate releases in themselves.
7fc3f7cf58