Crystal Reports Database Connection Precedence
Can anybody help me understand database connectivity precedence in Crystal Reports as well as Crystal Reports Server? I think I have too much information.
We are migrating from one SQL database to another and I need to move all the reports from VCU to VCUdm.
My questions are below -
1 - Under Set Datasource Location in Crystal Reports, there is an option for 'Use DSN default properties' that can be set to True or False. Is this referring to the Datasource Name on my local machine? If I change the ODBC connection to VCUdm will all references to VCU in the actual report be overridden by the DSN defaults? If the report is run on the server, does it default to the server DSN defaults?
2 - I have all the reports and report instances in the CMS using a custom database logon (so I don't need to enter the password each time I revise the report on the server). Do I need to update all the instances created with VCU to VCUdm or does the instance use the defaults from it's parent report (can I just change the report)?
3 - The ODBC connection is used on my local machine when I run reports locally. When is the ODBC connection used on the server that houses the CMS? Is it used when the reports are run through the CMS? Do I need to make sure both connections use VCUdm?
4 - I have some reports pulling across full tables and some reports pulling from a SQL command. Do I need to update my SQL command to say 'Use VCUdm' at the top as well as update the table datasource locations to say 'Catalog: VCUdm'?
Please see the attached PDF for a sample of one of my reports as seen through 'Set Datasource Location'.
I would appreciate any and all assistance - this really has me confused!!
Thank you.
Lisa
We are migrating from one SQL database to another and I need to move all the reports from VCU to VCUdm.
My questions are below -
1 - Under Set Datasource Location in Crystal Reports, there is an option for 'Use DSN default properties' that can be set to True or False. Is this referring to the Datasource Name on my local machine? If I change the ODBC connection to VCUdm will all references to VCU in the actual report be overridden by the DSN defaults? If the report is run on the server, does it default to the server DSN defaults?
2 - I have all the reports and report instances in the CMS using a custom database logon (so I don't need to enter the password each time I revise the report on the server). Do I need to update all the instances created with VCU to VCUdm or does the instance use the defaults from it's parent report (can I just change the report)?
3 - The ODBC connection is used on my local machine when I run reports locally. When is the ODBC connection used on the server that houses the CMS? Is it used when the reports are run through the CMS? Do I need to make sure both connections use VCUdm?
4 - I have some reports pulling across full tables and some reports pulling from a SQL command. Do I need to update my SQL command to say 'Use VCUdm' at the top as well as update the table datasource locations to say 'Catalog: VCUdm'?
Please see the attached PDF for a sample of one of my reports as seen through 'Set Datasource Location'.
I would appreciate any and all assistance - this really has me confused!!
Thank you.
Lisa
ASKER
Sorry - attached is the file.
Solicitation-Participation---Pag.pdf
Solicitation-Participation---Pag.pdf
Okay that looks like a report example, no data connection information, but that is okay.
Is changing the existing ODBC connection to your new connection string a possibility? If so, this seems like the easiest way for you to accomplish what you need to do.
Is changing the existing ODBC connection to your new connection string a possibility? If so, this seems like the easiest way for you to accomplish what you need to do.
ASKER
I guess that is where I am confused regarding which setting overrides which because the ODBC connections on both the server and on my local machine are set to the new database - VCUdm. But according to our sysadmin, the reports are all running off of the old database - VCU.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You also might want to do a verify database on the reports.
mlmcc
mlmcc
Otherwise, you will need to create a new ODBC connection (local and on the CR Server) and repoint all reports to use the new ODBC connection.