yolly12
MIS
- Mar 21, 2005
- 83
this is a sidebar to the question I asked the other day about ODBC.
I am running Crystal 8.5 developer, GoldMine 6.7, SQL 2000 and Windows 2003 standard sever.
If I create an ODBC File dsn to my SQL box and use windows authentication it runs just fine. that would mean that the NT login would have to exist locally on the machine with the ODBC connection and that is not a good idea for admin (over 200 users). If I take that same dsn and then say for it to use SQL authentication and create a user in SQL, the connection fails. The error states that either the server doesn't exist or access is restricted.
If I try to run the report I get the error listed in my subject line. Where does one set the security to allow login from an ODBC source?
thanks
I am running Crystal 8.5 developer, GoldMine 6.7, SQL 2000 and Windows 2003 standard sever.
If I create an ODBC File dsn to my SQL box and use windows authentication it runs just fine. that would mean that the NT login would have to exist locally on the machine with the ODBC connection and that is not a good idea for admin (over 200 users). If I take that same dsn and then say for it to use SQL authentication and create a user in SQL, the connection fails. The error states that either the server doesn't exist or access is restricted.
If I try to run the report I get the error listed in my subject line. Where does one set the security to allow login from an ODBC source?
thanks