ODBC Error on Reports

[CTekGirl]

I have created several Crystal reports using MSACCESS as the backend, with SQL SERVER being the true source of data. Basically the queries are written in Access, based on SQL SERVER tables.

I can run these reports repeatly no problem. However, when the user tries to run them they get an ODBC error failed to login, but it is showing the SQL SERVER database name.
I created a datasource based on the Access driver, but I get the same results. For some reason the report is trying to use the users NT ID instead of the ID for for SQL Server database, I believe that is the reason for the failure.

I deleted and re-created the datasources for both the Access and SQL Server datasources, but I get the same error.

Running this report on another machine, no problems. Help!

 

[synapsevampire]

The machine running the report will need the same ODBC setup as the developer.

"For some reason the report is trying to use the users NT ID instead of the ID for for SQL Server database" isn't very clear. The SQL Server ID is NOT embedded within the Crystal Report, if you have tables linked within an Access database, then a logon will be expected by Access, for security purposes it isn't stored within. If the developer selected Use Trusted Connection at the time they created the Link to the SQL Server tables, then it will use the login user/pw.

Not sure why you elected to use Access to link to SQL Server, this will only slow things down.

Hope this helps to describe the problem.

-k