> -----Original Message-----
> From: dryburghj@yahoo.com [SMTP:dryburghj@yahoo.com]
> Sent: Wednesday, November 10, 2004 3:41 AM
> To: informix-list@iiug.org
> Subject: Re: No ODBC access to Informix...
>
> Bill :
>
> "We have some kind of a pre-fab ERP solution in house. From any PC a
> telnet session is used to connect to the Solaris and to start the
> application."
>
> This does not use Informix ODBC and requires no informix networking
> utiilities on the PC.
>
> "So far reporting has been done using MS Query/ODBC."
>
> This does requrie Informix ODBC and does require informix networking
> utilities on the PC.
>
> Therefore only install the Informix networking utilities and ODBC
> driver on the PCs of the users that require this access. Don't let the
> other users know what the tcp port being used for this access is.
[Bill Dare]
This is what we are doing now except we also configure these ODBC
users to access a database with read-only views into the production
database. The problem is that the ODBC configuration does not require any
admin priveledge to make changes. So, there is the potential for some users
to tinker with the ODBC config and end up connected to the production
database.

Bill





> Bill Dare <dareb@jevic.com> wrote in message
> news:<1100020241.9Bar9R147kUlJjRAYe4IWQ@teranews>. ..
> > I am working with an old application here at Jevic that was written by
> the
> > Jevic ancients. And the ancients were not always wise. Security is
> > implemented at the application level, so it is required that each user
> log
> > in to his own account and that each user has insert/update/delete on
> every
> > table in the database.
> >
> > Regards,
>
sending to informix-list