Using A2003 but I guess this is not version-specific...
If I want to implement row/record level locking on a split database where
do I need to set this option. Is it sufficient to set it in the frontend
database for record-level locking to apply to the backend tables. Or must
I also set it in the backend mdb database instead or as well (which is
never 'opened' in an Access sense.
To take this further, what about a situation where some backend tables are
being shared between different frontend applications. Let's say there are
two applications, one requires record level locking and the other doesn't
and both apps are set 'correctly' for their own operation.
How does it work then because there is only one ldb file per backend?
(I'm leaving this Q as mdb-specific but obviously it could be continued
further)
Enlightenment welcomed.
Peter
Tell Access to open databases using record-level
locking by setting the record-level locking flag
in the FE database.
Databases will be used in the way they are opened,
so if one application opens a back end DB in page-locking
mode, all applications will use it that way. If a
different application opens it first in record-locking
mode, all applications will use it like that.
(david)
> Using A2003 but I guess this is not version-specific...
>
[quoted text clipped - 16 lines]
>
> Peter
Peter - 28 Apr 2005 07:46 GMT
Thanks.(david)
That is i what I suspected so your confirmation is helpful in the issue I am
dealing with.
Peter
> Tell Access to open databases using record-level
> locking by setting the record-level locking flag
[quoted text clipped - 31 lines]
>>
>> Peter