|
| OK, thanks for clarifying what you were referring to. Still, that would be
handled on a per-machine basis, and this is something that changed in the
database (either SQL back end or front end MDB), since it happened across
the board, both locally and across the LAN.
N
"david epsom dot com dot au" < david@epsomdotcomdot
au> wrote in message
news:OFQvvDwOFHA.1528@TK2MSFTNGP09.phx.gbl...
> The Option that is labelled "Open databases using record-level
> locking" controls the way databases are opened. The options
> are record-level locking and page-level locking. Another
> 'kind' of locking is table-level locking. At the engine level,
> these are the kinds of locks that are used.
>
> The decisions about WHEN to lock (early, late, never,
> optimistically, pessimistically etc) are controlled
> separately, for example by form properties.
>
> Theoretically, there is no reason why the lock scope should
> affect the data transfer strategy, but I have noticed some
> odd effects of this setting, which is why I suggested that
> you try changing it.
>
> (david)
>
>
> "Neil" <njones@pxdy.com> wrote in message
> news:VGG4e.1212$lP1.487@newsread1.news.pas.earthlink.net...
>
>
|
|