Re: ODBC with Informix

You could use Easysoft, ODBC for ISAM to access the Informix database - that way users can be assigned privileges carry out SQL Select, Insert, Delete and Update functions For more info see: http://www.easysoft.com/products/ Glyn_Balmer_at_erith@smtpgwy.supertension.com wrote in article <6f6ake$cpa$1@news.xmission.com>... > > Matt Reprogle wrote : > > > Jay Hannah wrote: > > > > > > Killspamrs wrote: > > > > Along this line, but completely different, in an NT/win 95 > > environment is it possible to completely disable all ODBC > > connectivity from within Informix? I > > > <snip!> > > > Since syscolsauth will say they have add/change/delete god knows > what they > > could do. > > > > If you don't trust these users w/ delete/mod access, why do they > > have it in the first place? Revoke priviledges in Informix, and > > they're locked > > out no matter what client (ODBC or otherwise) they use. > > > Have I missed something? > > > > Jay > > > Perhaps. In some situations, users have an "approved" application > > through which they are allowed to perform modifications, but you do > > not want them to have unrestricted SQL-level access through > > ODBC-enabled tools like MS-Query. > > Agreed. We admininster a package wherein the end user requires all > permissions on all tables in order to be able to carry out their > normal job function. However, we also need to give ODBC access to > certain individuals to enable database access via MSOffice, for > example. Therein lies our quandary. Since the user has a pukka (UNIX) > login to the database with full permissions, how do we prevent him/her > attaching via ODBC as the same user and thereby open the flood gates ? > > At the present moment in time this is still an unresolved problem to > us. > > Regards > > Glyn Balmer > I.T. Consultant > BICC Cables Limited > Erith Kent UK >