Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
Just SET LOCK MODE TO WAIT 10; then the client session will wait for
10 seconds for any transient locks to clear before returning a lock error.
Unless your apps are poorly designed most locks are transient so this is
the correct solution.
Art S. Kagel
nonbeliever wrote:
>
> We may be a little behind the times, so bear with me on this one :)
>
> We just upgraded from "Standard" engine to "Workgroup" Informix engine.
> Since doing that we are getting record locks - OK no problem with dbaccess -
> just use 'set isolation dirty read'. Big problem with Microsoft Access
> using the Merant ODBC drivers. We can not find a way to make MS Access
> utilize the dirty read. Instead all we get are ODBC errors indicating
> record locks.
>
> Can anyone let me know how to set MS Access to dirty read?
>
> Thank you all in advance - this is my first time posting, but have read this
> board for a couple of weeks and learned many new (to me anyway) things!
> Keep up the good work!
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.