Re: ODBC and Security

In Article<3143049B.6FB4@rl.is>, <john@rl.is> writes: > > Irwin, > > For a newbie, you certainly come up with good answers > >[Snip!] > > I still think my original solution is most secure, which I'll repeat: > > Setup your users with read-only access to the database. Create one user > called "program" which has read/write access. Regardless of the user, > the central application connects to the database as user "program", > having the password hard coded. In this way, the central application > is the only client modifying data. Users can connect using ODBC or > anything else using their own id's to query and produce reports. > >[Snip!] > John, I agree with most of what you have written in this thread (in particular, when you say that 4gl is still adequate for most users needs). I cannot but note however that your solution does not address the problem of granting different rights to different users. marco. ____________________________________________________________________________ rem radioterapia, which I immeritately manage, seldom agrees with what I say marco greco (Catania, Italy) Work: marcog@ctonline.it rem radioterapia 39 95 447828 fax 446558 (was mar.greco@agora.stm.it) Achea 39 95 503117