v_pushparaj
asked on
How to Prevent Dialog box requesting ODBC Logon information
A new Report is created off an Microsoft Acess 97(Acess) Database,Via ODBC.The acess database contains linked sql server tables.The initial connection from crystal reports to the database is sucessful and data from the attached sql server tables is returned correctly.the report is saved,and closed and then reopened sucessfully.However upon refreshing the report,the dialog box appears requesting Sql server ODBC logon information.How to prevent this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Maybe you can try to connect with Access directly using Crystal's native Access driver instead of using an ODBC connection.
-psyberfry
-psyberfry
can you configure the ODBC setup for the SQL server to have a username and password preset?
Don't know why you have to use the Access97 to SQL server? If you could go direct to SQL server using ODBC or OLEDB, I've got a solution:
1) For ODBC, you can use File DSN, and then open this File DSN in Notepage, and enter this into it:
UID=yourUserName
PWD=yourPassword;
and then you could create a report off this FileDSN, you should be able to run report without prompt;
2) For OLEDB, you can create a report off OLEDB source, and then from the OLEDB GUI there is a option ("Save password") make sure that you've checked that and then put in the password;
Last, if your SQL server database accept NT Authentication, then you could simply create a report using that ("Trust Connection"), and this way the report will also not prompt you for password. However, you will have to keep one thing in mind, which is that all above will ONLY work in designer and will NOT work from any runtime environment. I hope this helps.
1) For ODBC, you can use File DSN, and then open this File DSN in Notepage, and enter this into it:
UID=yourUserName
PWD=yourPassword;
and then you could create a report off this FileDSN, you should be able to run report without prompt;
2) For OLEDB, you can create a report off OLEDB source, and then from the OLEDB GUI there is a option ("Save password") make sure that you've checked that and then put in the password;
Last, if your SQL server database accept NT Authentication, then you could simply create a report using that ("Trust Connection"), and this way the report will also not prompt you for password. However, you will have to keep one thing in mind, which is that all above will ONLY work in designer and will NOT work from any runtime environment. I hope this helps.
ASKER
Thanks Mr jsweby.it helped me a lot a lot .now i am not getting the problem
Mr. jsweby whats the URL of crystal community
I cann't find Track ID 27800
Please reply me Cannot fint Track ID 278000 :(
"This is a known issue with SCR and has been assigned Track ID 27800."
J.