Preview and print a Crystal report prompted for the sa password

Question

Dear All,
Our customer has Crystal report add-on to be installed. When we Preview and print a Crystal report, we got a window prompted for the sa password. Even we type in a correct password, it still says wrong password...
Every time when I open my report in Crystal Basic 2008 on the server, then go database expert >> My connections >> click + in front of the connection name, it asks my sa password. I type in my password then save and close. Next time when I open the report and go my connections, I have to type in my password again. This only happens on one customer.
Any idea? Thanks a lot.
Regards,
Yuka

Answer 1

Hi Yuka,
1) All their SAP client workstation, they have to have use SQL2008 CD and install SQL Client on it
Correct, MS does NOT support MDAC or WDAC when connecting to SQL 2008.
2) Then go ODBC >> SQL Native Client 10.0 >> Create a new connection to SAP server. Should we use sa user or another use that has the same authorization as sa?
Correct again if they are also using ODBC to connect, as for using the sa account or creating a new one is up to you. I suggest creating a Crystal account with what ever rights your app needs, this way if tracing it turned on etc. you can confirm who is actually running the report.
3) Then from MY Crystal report, I have to use ODBC connection as well?
Just to clarify, if you created your reprots using OLE DB then they can do so also. But you need to update your connection properties. Open each report click on Database, Set Location, scroll down to OLE DB and expand and then choose MS SQL Server Native 10 as your OLE DB provider, fill in all the logon info and then verify the database. Do the same for each subreport also.
Save your report and either send them the new one or if you are doing this remotely then replace the original report.
VERIFY your reports to confirm they still return correct data and do work as expected.
Or if you are using ODBC then yes you do select the MS 10 driver with a new DSN. Then do the above to update the reports to all use ODBC as their data sources.
Hope this is all clear now....
Thanks again
Don