MS Excel 2000
IDS 9.30 UC1
Dynix/ptx V4.5.3
Thanks
N.
Bottom line, if the user has odbc access to your database then
they can submit any valid SQL statement, it is up to the
DBA to prevent the engine from allowing it to execute.
--
Paul Watson #
Oninit Ltd # Growing old is mandatory
Tel: +44 1436 672201 # Growing up is optional
Fax: +44 1436 678693 #
Mob: +44 7818 003457 #
www.oninit.com #
Hello N.,
What ODBC drivers are you using? Native? I know that my own company's drivers implement a variety of features, which are designed to prevent unauthorized database updates. They range from simple read-only check boxes on the client to advanced server-side security rules. Quite possibly, your driver may have such features?
Netrista Khatam
Technical Services Manager
OpenLink Software
Universal Data Access & Virtual Database Technology Providers
http://www.openlinksw.com
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