471,089 Members | 1,577 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,089 software developers and data experts.

ODBC Connection

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

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.

Nov 12 '05 #1
0 1688

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Sean Anderson | last post: by
5 posts views Thread by SerGioGio | last post: by
11 posts views Thread by DJJ | last post: by
5 posts views Thread by Alec | last post: by
4 posts views Thread by Dave | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.