Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion


Crystal Reports & SQL Server

By bob ·
We have developed some Crystal Reports in a VB app we are building for a client. Initially the Reports hit our development database. We have now imported real data into another database on the same server. We need to change the connection string on these reports to point to a different Initial Catalog. However, this isn't something that CR seems to want to do. Does anybody out there have any expertise in CR and could tell me how to change the database it is pointing to?

We tried Set Location, but it only wants to reference a single table, and the query string references more than one table.

We need to figure this out, because 1. I need to start beta testing right away, and 2. when we move it to their production server, it willneed to be changed again.

Thanks for any and all help!!!


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

stored procedures

by shelleydoll In reply to Crystal Reports & SQL Ser ...

I worked with a team last year that ran into this exact issue. We were using MS SQL Server for our database, and wound up pointing the reports to stored procedures (we had to create one for each report). We also tried virtual tables, but I honestly don't remember why we didn't stick with that path. Sorry I'm not more help!

BTW - Your email message about the discussion board was forwarded to our team. Just wanted to let you know so you don't think it disappeared into a void somewhere.

Collapse -

easy solution

by Aaron_kempf In reply to Crystal Reports & SQL Ser ...

the easy solution is to throw away crystal reports and use Access Data Projects.

these have one centralized location for login information; and this is easy to change programmatically.

additonally, these have the _best_ SP development tools around-- (Access 2002).

Take a look at Northwind.adp (it might be called NorthwindCS.adp).

these are Access 2000 or 2002 compatable; and if your client doesn't have access on the desktops, implement the access runtime. (and if they do; then convince them to move to the runtime)

Related Discussions

Related Forums