"N" <N@N.COM> wrote in message news:<WkMIa.917$Wl1.710@newssvr19.news.prodigy.com >...
> Hi all,
> I set up an Excel spreadsheet to our production database
> through ODBC driver to get a report. Everything was working
> fine, and life was good until I found a little problem with the
> SQL tool in Excel. Normally, to get a report Excel will write
> a select statement according to criterias that the users input/
> choose. It also allows anyone to Edit the select statement it
> writes in a little box. What I did was changing that select
> statement to delete/update statement. And it ran. What
> surprised me was that it actually ran the statement against
> the database and delete/update tables accordingly. This is
> not what we want. I have not been able to find any options
> to turn this thing off so that the user cannot edit the generated
> select SQL. I know all the permissions the user has are
> defined through the username that is defined in ODBC.
> We don't want to change all the user permissions on the
> database side. Is there any other way ?
>
> MS Excel 2000
> IDS 9.30 UC1
> Dynix/ptx V4.5.3
>
> Thanks
> N.

Your problem is only resolved by using a driver that enables you to
configure conditional behavior (OpenLink Software provides Multi-Tier
ODBC Drivers with this capability). In this case the Driver could be
configured to ensure that if Excel is the ODBC client all ODBC
connections will be read-only. You can even be more granular, and
have the driver actually permit specific users to have read-write
capabilities from Excel depending on the rules that you set.

You can download these drivers on a free evaluation basis from:
http://www.openlinksw.com


Regards,
Kingsley Idehen
OpenLink Software
http://www.openlinksw.com/blog/~kidehen