Re: Dirty Read via ODBC?

In article <01bca11a$1fd314c0$a00101c0@bis005392>, jlusty@wrbc.com says... >There doesn't seem to be a way to set the Isolation Level to Dirty Read >within the CLI components (SetNet32, Informix ODBC driver ver. 2.5). In >this case, we are using MS Access as a front end, but will likely be moving >to Seagate Crystal Reports. ODBC does provide a way to do it (SQLSetConnectOption, with SQL_TXN_ISOLATION set to SQL_TXN_READ_UNCOMMITTED). As Nils said, if the tool you want to use doesn't support the capability, it is a deficiency in the tool that you'll have to fix either by using a different tool or by going to an ODBC driver that provides some behind-the-scenes way to do this. -- William Harris william@carsinfo.com Check out the NAGS spam filter. http://www.cs.hmc.edu/~ivl/nags/index.html