ODBC system dsn problem

We have a client that is trying to connect to a SQL DB on
a Win2003 server (thru Citrix) using a system dsn. When a
user tries connecting using the system dsn in Crystal
Reports (or anyting else for that matter), they get the
following error: data source name not found and no default
driver specified.
If you go into the ODBC manager, the data source is there
but when you try to configure it you get - dsnname is not
an existing data source name. when you click on ok you
then get - invalid dsn.
If you log onto the workstation as a user with
administrator rights, none of these errors occur.
I have looked at our Citrix machine and 2 other customer
Citrix machines that are running the same software and I
realy don't see any differences. Our's and the other 2
customers work without the user having admin privleges.
Everything points to a permissions problem but whatever it
is, is alluding me. any help at this point is appreciated.
TIA,
BillODBC entries are controlled in the registry. I would suggest using
regedt32 or regedit (if you are on Win 20003/XP), and go to
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC and try adding full control permissions
for the affected user/groups, replacing the values in the subkeys. Good
luck.
****************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
This posting is provided "as is" with
no warranties and confers no rights.
****************************************
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Thanks Andy. I received a similar response on a SQL Mail
list that I posted to. The registry seems to have been the
problem. I changed the permissions giving access to the
everyone group. I then tested going into the odbc
configuration as one of the users that was having problems
and I no longer get an error. I have the customer testing
an Access program that has linked tables using the system
dsn.
Bill

>--Original Message--
>ODBC entries are controlled in the registry. I would
suggest using
>regedt32 or regedit (if you are on Win 20003/XP), and go
to
>HKEY_LOCAL_MACHINE\SOFTWARE\ODBC and try adding full
control permissions
>for the affected user/groups, replacing the values in the
subkeys. Good
>luck.
> ****************************************
>Andy S.
>MCSE NT/2000, MCDBA SQL 7/2000
>andymcdba1@.NOMORESPAM.yahoo.com
>Please remove NOMORESPAM before replying.
>This posting is provided "as is" with
>no warranties and confers no rights.
> ****************************************
>*** Sent via Developersdex http://www.examnotes.net
***
>Don't just participate in USENET...get rewarded for it!
>.
>

ODBC Secruity

I have set up a VB front end and use an ODBC to connect to
an SQL database. Is there a way were i can not allow a
user to simply connect to their ODBC link and Delete the
whole thing using access?If the user has access to the server and a login, there's not much you can
do to stop a particular method of accessing the server. If you application
lived on a web server, you could restrict access to the SQL Server from
only that machine using IPSec policies. But, there isn't a good way to
restrict access via ODBC or dbLibrary api for example.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.