Crystal Reports

[Keiko]

Try to complete the connection string.
If it's a correct connection, then
your CR will not ask for any more info from you.

Regards

[Dawnc]

What do you mean by "complete the connection string"? Dawn

[Keiko]

By specifying user_id, password, or dsn name.
for example:

Object.ConnectionString = "UID=admin;Password=abc;DSN=MyAccess"

Regards
Keiko

[murtagh]

I had a problem some what simular to this with seagate analysis, and both analysis and crystal use the same procedures, this should work.


Synopsis

In Seagate Analysis, when trying to add a table from an Access 97 database (with no database level security) via ODBC, you are prompted for a 'User ID' and 'Password'. Once you have filled out the 'User ID' and 'Password' boxes and clicked 'OK', the following error message occurs:

"Cannot Open SQL Server"

Details:
SQL server logon failed
Y:\ashwin\DTS\DTSagent\ReportHandler.cpp(636)
CRPE error: 599
Error Message: Cannot Open SQL Server



Solution

The error message occurs when the Access 97 ODBC data source is not configured to point to a specific database file (*.mdb). Once the data source is properly configured in the ODBC Administrator, you will not receive the error message.

To configure the Access 97 ODBC Data source:

1. Start the ODBC Data Source Administrator.
2. Select the "User DSN" tab.
3. In the 'User Data Sources' box, select 'MS Access 97 Database'.
4. Click 'Configure'. The 'ODBC Microsoft Access Setup' dialog box appears.
5. Under 'Database', click 'Select'.
6. Browse for the desired *.mdb file and click 'OK'.
7. You should now see the full path to the *.mdb file under 'Database'.
8. Click 'OK' to close the 'ODBC Microsoft Access Setup' dialog box.
9. Click 'OK' again to close the ODBC Data Source Administrator.
10. Re-open Seagate Analysis (or in your case Crystal Reports) and try the connection again.

Once the ODBC data source has been configured correctly, the error message will not be received.

This issue has been assigned to Track ID 37756.

NOTE: ========
This behaviour occurs with all file types using the ODBCJT32.DLL driver, such as FoxPro, Paradox and dBase database files. The solution outlined in this article applies to these file types as well.
===============



--------------------------------------------------------------------------------