By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,500 Members | 830 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,500 IT Pros & Developers. It's quick & easy.

ODBC Connection

P: n/a
Hi all,

I've got users with an ODBC connection to a SQL Server database. The
problem is that once users get that ODBC Connection from their network
administrator, they can access any table and potentially delete any
data. It's wide open. I know I can tighten security through SQL
Server, but what I'd like to do is use an existing Access application
that is connecting to the SQL Server database via that ODBC connectino
to build me a DSN on the fly. Or somehow use a connection that is
visible only through code that they cannot access. Can this be done?

Ideally, the user would open the Access application (preferably an mde
file) and through it, the connection would be created. A book shows me
that I may be able to use a connection string something like
DSN=data-source;UID=user-id;PWD=password;DATABASE=database

It seems to me that even if I were to do that, Access would be using a
DSN that could be found in the ODBC Administrator. What I want to do
is keep the user from seeing/using that connection, or at the very
least, use a password that is supplied by the Access app and not
something they have access to. This way, they cannot just go into
Access, attach a few tables, and have free reign.

Can this be done?

Thanks in advance.

Andrew
Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.