Setting data source location - need workaround

[mwhalen]

Is there a way around having to change the datasource location every time I send a report back and forth to a client? Her database name is different than mine and it's getting cumbersome when I do work on it and have to send it back and forth.

Does anyone know of a workaround? I'm using Version 9

 

[bdreed35]

If you were using ODBC, you could create System DSN's on both machines that were named the same. The DSN's could be set up to the different data sources, thus not effeecting the report. This would allow you to send the reprt without having to set the location everytime.

~Brian

 

[SFLLC]

If you don't mind a third party utility, our new .rpt Inspector 2 Professional Suite now comes in two editions. One that supports CR5.x-CR8.5 and one that supports CR9.x. Everything else in the two editions is the same. Including support of a new "data source / database conversion and migration wizard" which allows you to select one or more reports and select multiple sources to a destination for set location, convert driver, verify database. And we support ODBC / OLE DB / Native DB2 / Native Informix / Native Oracle / Native SQL Server / Native Sybase.

Both editions are now available for a FREE 30-day trial download.

Software Forces, LLC

http://www.softwareforces.com

===> two editions released: ".rpt Inspector 2 Professional Suite (for CR5.x-CR8.5)" and ".rpt Inspector 2 Professional Suite (for CR9.x)"
=====> download your FREE 30-day trial today!

proud makers of ".rpt Inspector" brand for Crystal Reports,
"SPL (Smart Pick Lists)" for Crystal Enterprise, and "SmartObjects" for Seagate Info & Crystal Enterprise.

Coming soon ".rpt Inspector 3 Enterprise Suite" for Crystal Enterprise