Crystal Report Viewer Credential Prompt for Report with Dynamic Parameters

Question

The .NET Crystal Report Viewer is prompting for database credentials when launching a report containing dynamic parameters. This only occurs for reports created with SAP Crystal Reports 2011 designer. Reports created with Crystal Reports XI designer (where dynamic parameters were first introduced) work correctly.
The credential prompt window contains the following fields:
- Server Name: <server name> (disabled)
- Database Name: <database name> (disabled)
- User Name: <empty> (enabled)
- Password: <empty> (enabled)
- Use Single Signon Key: false (disabled)
The values in the prompt window which are disabled are the database connection values used during the design of the report in the SAP Crystal Reports 2011 designer.
Expected Result:
- No prompt for database credentials.
- Values read from the database should be populated in a drop down for the dynamic parameters.
Environment:
- Visual Studio 2010 (C#)
- Windows 7 Enterprise
- SAP Crystal Reports runtime engine for .NET Framework 4
- SAP Crystal Reports, version for Visual Studio 2010
- SAP Crystal Reports 2011
The database connection is being set to use a DSN. It must be a DSN as the calling application is only aware of the DSN/Username/Password values. These values are being passed to the Crystal Report Viewer contained in a Windows form.
The database connection for the report is being set as follows:
foreach (InternalConnectionInfo internalConnectionInfo in this.report.DataSourceConnections)
    // Must set the UseDSNProperties flag to True before setting the database connection otherwise the connection does not work
    if (internalConnectionInfo.LogonProperties.ContainsKey("UseDSNProperties"))
        internalConnectionInfo.LogonProperties.Set("UseDSNProperties", true);
    // Supposed to set the database connection for all objects in the report (ie. main report, tables, sub reports)
    internalConnectionInfo.SetConnection(this.DSN, string.Empty, this.LoginName, this.Password);
The SetConnection method's signature is as follows:
   SetConnection(string server, string database, string name, string password)
As you can see from the code snippet above I am setting the DSN name as the server parameter, blank for the database parameter (a database connection using DSN should only require DSN name/Username/Password) and the database username and password respectively.
Is this a SAP bug?
Is this the correct way of setting the database connection to use a DSN?
Is there some other properties that need to be set somewhere else in the report through code?
Any help would be greatly appreciated.

Answer 1

Thanks for the pointer to the database connection code generator. After taking a look at the output from the tool I was able to finally get the dynamic parameters to load and populate properly without prompting for credentials. I needed to tweak the outputted code a bit to match my requirements of using a DSN only connection.
Instead of updating the database connection properties contained within the Report.Database.Tables collection from the CrystalReports.Engine namespace, I changed it to replace the database connection properties in the Report.ReportClientDocument.DatabaseController.Database.Tables collection from the CrystalDecisions.ReportAppServer.DataDefModel namespace. For one reason or another, using the RAS namespace solved the problem.
Below is the updated code with the change made:
using RAPTable = CrystalDecisions.ReportAppServer.DataDefModel.Table;
foreach (InternalConnectionInfo internalConnectionInfo in this.report.DataSourceConnections)
    // Must set the UseDSNProperties flag to True before setting the database connection
    if (internalConnectionInfo.LogonProperties.ContainsKey("UseDSNProperties"))
        internalConnectionInfo.LogonProperties.Set("UseDSNProperties", true);
    // Sets the database connection for all objects in the report (ie. main report, tables, sub reports)
    internalConnectionInfo.SetConnection(this.DSN, string.Empty, this.LoginName, this.Password);
// The attributes for the QE_LogonProperties which is part of the main property bag
PropertyBag innerPropertyBag = new PropertyBag();
innerPropertyBag.Add("DSN", this.DSN);
innerPropertyBag.Add("UserID", this.LoginName);
innerPropertyBag.Add("Password", this.Password);
innerPropertyBag.Add("UseDSNProperties", "true");
// The attributes collection of the tables ConnectionInfo object
PropertyBag mainPropertyBag = new PropertyBag();
mainPropertyBag.Add("Database DLL", "crdb_ado.dll");
mainPropertyBag.Add("QE_DatabaseType", "OLE DB (ADO)");
mainPropertyBag.Add("QE_LogonProperties", innerPropertyBag);
// Pass the database properties to a connection info object
ConnectionInfo connectionInfo = new ConnectionInfo();
connectionInfo.Attributes = mainPropertyBag;
connectionInfo.Kind = CrConnectionInfoKindEnum.crConnectionInfoKindCRQE;
connectionInfo.UserName = this.LoginName;
connectionInfo.Password = this.Password;
// Replace the database connection properties of each table in the report
foreach (RAPTable oldTable in this.report.ReportClientDocument.DatabaseController.Database.Tables)
    RAPTable table = new RAPTable();
    table.ConnectionInfo = connectionInfo;
    table.Name = oldTable.Name;
    table.QualifiedName = oldTable.QualifiedName;
    table.Alias = oldTable.Alias;
    this.report.ReportClientDocument.DatabaseController.SetTableLocation(oldTable, table);
this.report.VerifyDatabase();
Thanks again Ludek for the help.