"Log on failed" with ODBC and Stored Procedure

Question

I am in the process of porting our application from CR10 to CR.NET and am having some trouble setting the log on info.
I have a report that was designed against a stored procedure and a development database.  The connection at design time is ODBC to a SQL Server.  At runtime I want to set the database and logon credentials to that of the production server, set the stored procedure parameters, and then display the report.  No matter what I do always get "Log on failed" error.
After having considerable trouble with ApplyLogOnInfo on the tables where it seemed to not actually apply my changes, I finally found code which appeared to work elsewhere on this forum.  So this is the code that I have now, but the call to VerifyDatabase on the report always throws the Log on Failed exception:-
void SomeClass::SetLogOnInfoForReportRecursively(ReportDocument^ ReportObj)
        CrystalDecisions::Shared::TableLogOnInfo^ l_pTableLogOnInfoToSet = gcnew CrystalDecisions::Shared::TableLogOnInfo();
        CrystalDecisions::Shared::ConnectionInfo^ l_pConnectionInfo = l_pTableLogOnInfoToSet->ConnectionInfo;
        l_pConnectionInfo->AllowCustomConnection = true;
        l_pConnectionInfo->ServerName = gcnew String(m_strServerName);
        l_pConnectionInfo->DatabaseName = gcnew String(m_strDatabaseName);
        l_pConnectionInfo->UserID = gcnew String(m_strUserID);
        l_pConnectionInfo->Password = gcnew String(m_strPassword);
        DbConnectionAttributes^ l_pConnectionAttributes = gcnew DbConnectionAttributes();
        l_pConnectionAttributes->Collection->Set("Database DLL", "crdb_odbc.dll");
        l_pConnectionAttributes->Collection->Set("QE_DatabaseName", String::Empty);
        l_pConnectionAttributes->Collection->Set("QE_DatabaseType", "ODBC (RDO)");
        l_pConnectionAttributes->Collection->Set("QE_SQLDB", true);
        l_pConnectionAttributes->Collection->Set("SSO Enabled", false);
        l_pConnectionInfo->Attributes = l_pConnectionAttributes;
        //main connection
        ReportObj->SetDatabaseLogon(l_pConnectionInfo->UserID, l_pConnectionInfo->Password, l_pConnectionInfo->ServerName, l_pConnectionInfo->DatabaseName, false);
        //other connections
        for each(CrystalDecisions::Shared::IConnectionInfo^ pConnection in ReportObj->DataSourceConnections)
            pConnection->SetConnection(l_pConnectionInfo->ServerName, l_pConnectionInfo->DatabaseName, l_pConnectionInfo->UserID, l_pConnectionInfo->Password);
            //pConnection->SetLogon(l_pConnectionInfo->UserID, l_pConnectionInfo->Password);
            pConnection->LogonProperties->Set("Data Source", l_pConnectionInfo->ServerName);
            pConnection->LogonProperties->Set("Initial Catalog", l_pConnectionInfo->DatabaseName);
        // Now we need to set the log on info for any subreports otherwise they will always look for the datasource they were set up with.
        if (!ReportObj->IsSubreport)
        for each (ReportDocument^ l_pSubReport in ReportObj->Subreports)
             SetLogOnInfoForReportRecursively(l_pSubReport);
        for each (CrystalDecisions::CrystalReports::Engine::Table^ l_pTable in ReportObj->Database->Tables)
            TableLogOnInfo^ l_pCurentTableLogOnInfo = l_pTable->LogOnInfo;
            l_pCurentTableLogOnInfo->ConnectionInfo = l_pTableLogOnInfoToSet->ConnectionInfo;
            l_pTable->ApplyLogOnInfo(l_pCurentTableLogOnInfo);
            if (!l_pTable->TestConnectivity())
               // handle error situation
... then the calling code
SetLogOnInfoForReportRecursively( pReportObj );
// l_Parameters contains the stored proc param name/values pairs to set at runtime
for each (KeyValuePair<String^, String^> param in l_Parameters)
        pReportObj->SetParameterValue(param.Key, param.Value);
pReportObj->VerifyDatabase();
which then fails.  Can anyone see what I am doing wrong?
Thanks

Answer 1

Hi Paul,
Are you using CR for VS SP 13? If not you can get it here:
SAP Crystal Reports, developer version for Microsoft Visual Studio: Updates & Runtime Downloads
And MS SQL Server does not use a blank database name:
l_pConnectionAttributes->Collection->Set("QE_DatabaseName", String::Empty);
Set it to a database used in the report.
And you don't need to call .Verify, unless the reports are not up to date, which is not recommended, you should be using ReplaceConnection. ( Search for this, KBA's and posts on how to use it )
So rather that call .Verify try CRTable.TestConnectivity();
If that fails then you know your log on failed also.
Curious, if you try to preview the report it should prompt for log on info, if the Server and Database names are grayed out ( not editable ) then CR can't find the client either.
And MS recommends using the client that matches the version of SQL Server, So if 2005 and less you can use the MDAC SQL Client driver, for MS 2008 then use the SQL Native 10 or above.
Don