SQL, Crystal Reports, and VS.Net version conflicts

[dlima]

I have the following Software Installed on 2000 server box:

A) SQL Server 2000

B) Crystal Reports 8.5 Developer

C) Visual Studio .Net Professional version 2002

Everything is working fine except I can run reports that are already made.

We used to run these reports on a 2000 server box with the following Software Installed:

A) MS Assess 2000 (Instead of MS SQL)

B) Crystal Reports 8.5 Developer

C) Visual Studio .Net Professional version 2002

So I am wondering two things:
1) Does SQL server have a version of Crystal reports/designer built in.
If this is true?
2) Do I have a version conflict issue?

The reason why I am pondering that possibility is the following:
When I look into windows explorer- (c:\Program files\Common files\Crystal Decision)
What I see are two folders. One labeled 1.0 and the other 2.0

Any ideas based on your experience are appreciated.

 

[mrdenny]

1. No.
2. Probably. Sounds like it.

Is this a totaly new server? If so did you install the Crystal part of Visual Studio?

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[SQLSister]

Generally SQL Server should not be running onthe same box with other applications.

Questions about posting. See faq183-874
Click here to learn Ways to help with Tsunami Relief

 

[aftertaf]

sql server doesnt have CR built in,
but vs.net 2002/2003 does.
it has CR9 for .net!!

Aftertaf

"Resolve is never stronger than the night before it was never weaker

 

[SQLBill]

Lastly, you say your problem is with running reports you already created.

You created those reports to run against a Microsoft Access database and now you are using a Microsoft SQL Server database. They aren't the same thing. While there is a basic SQL similarity in commnands, SQL Server's TSQL is not completely the same as the SQL used in Access. For example: Access has IIF, SQL Server doesn't. There are other compatibility issues that you might be having problems with.

-SQLBill

Posting advice: FAQ481-4875

 

[Catadmin]

Side note on what SQLBill said: Have you tried either changing the data source for your previous created reports to point to the SQL Server or creating a brand new data source that points to the SQL Server?

You'll need to do one of the two, then, with the reports in edit mode, either Verify Database or Set Location (both under the Database menu) for your reports to work correctly.

If you haven't done any of this, then you need to before proceeding with any other SQL Server troubleshooting. Once you've done all this, hit the lightning bolt in CR (preview) and see if the reports work. If they still have a problem, it's probably more a CR problem than a SQL issue.



Catadmin - MCDBA, MCSA
Remember, "Work" is a four letter word. And you know what your mother told you about using four letter words!