Re: How to DISSALOW ODBC usage

From: Heinz Kiosk <no.spam_at_ntlworld.com>
Date: Wed, 20 Feb 2002 09:28:02 -0000
Message-ID: <21Kc8.89976$as2.14673742@news6-win.server.ntlworld.com>

One solution I have seen to this general class of problem is for your app to supply a private password (dsn=?;uid=?;pwd=?) to the ODBC connection. Then set up your ODBC connections on your client PCs yourself, and don't tell the users the password. Or ship the app with a command-line that includes a mangled version of the password so that the app can fire a dsn-less connection. . Some variation on these kind of ideas should work for you I hope.

All a bit of a kludge really, I bet those smart Oracle dbas will give you a much better solution, probably involving some kind of server side "Who is logging in?" trick.

Regards

"Andreas Wizemann" <AWizemann_at_fvvag.de> wrote in message news:8oi27us3va0sma79o0pdm3je49g1udsk3v_at_4ax.com...
> Hi,
> how can i prevent a user from doing a odbc connect against my database
> ?
> All users have (some) read/write permissions granted to their userid
> and access to the data is checked by a forms application to prevent
> from missusage. But if the user "knows" about ODBC, he can access the
> database directly without the forms appl.
>
> Any hints ?
>
> Regards
> Andreas Wizemann
Received on Wed Feb 20 2002 - 03:28:02 CST