Crystal Reports DataSource

[ChiTownDiva]

This problem is weird and it's probably because until now, I haven't used Crystal much.

In Crystal Reports (8.5), the datasource that we use for reports is called "PROD". It's located in the folder "More DataSources" under "Oracle Server", "PROD". I saved this to my "Favorites" folder and the reports that are designed through Crystal Reports run off it and they run fine. When publishing these reports to Crystal Enterprise--they run fine. Also when you log into the server the following comes up "Oracle SQL", User ID, Password, Server" and you type in "PROD" for the server.

BUT when I used Crystal Designer, I can't find "PROD"--just the typical ODBC Oracle servers (CROR8, CR0R8V36). When I try to long on the following comes up: "Logon to Oracle 8, Server Name: Prod, User Name: tedsrpt, Password:". Am I wrong to assume that "PROD" is a part of one of these servers?

Also, this is creating another problem I mentioned in another thread. When I create reports using SQL Query Designer and publish them through Enterprise, when I go to run an instance I get a "Failed" with a "Not Enough Memory for Operation" error message.

I'm lost.

Thanks.

 

[lyanch]

You are designing reports under the "native" connection. SQL Query Designer only uses ODBC source. If you want to use the SQL Query Designer you must set up an ODBC source.

As a side.. my personal recommendation is to avoid SQL Query Designer. If you have items that you can't handle in Crystal itself, a stored procedure is probably the better way to go.

Lisa

 

[ChiTownDiva]

Thanks Lisa...

Well, I guess this gives me an opportunity to try to write procedures.

The problem with writing a lot of our reports in straight Crystal is that it bogs down the Enterprise Server because each report pulls in way too many records. (i.e... a report that only uses 300 records actually pulls in 10,000 and the other 9,700 are "grouped out", (not a very efficient way to design reports), well you multiply that by a couple of hundred users and...well you see where I'm going...