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