|
Home > Archive > MS Access Multiuser > April 2005 > Record level locking in mdb -frontend?-backend? both?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Record level locking in mdb -frontend?-backend? both?
|
|
| Peter Russell 2005-04-21, 7:24 am |
| 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
| |
| david epsom dot com dot au 2005-04-26, 8:25 pm |
| 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)
"Peter Russell" <rusty@127.0.0.1> wrote in message
news:memo.20050421130954.1752A@russellscott.btinternet.com...
> 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
>
| |
|
| Thanks.(david)
That is i what I suspected so your confirmation is helpful in the issue I am
dealing with.
Peter
"david epsom dot com dot au" < david@epsomdotcomdot
au> wrote in message
news:uJoUgOsSFHA.580@TK2MSFTNGP15.phx.gbl...
> 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)
>
>
> "Peter Russell" <rusty@127.0.0.1> wrote in message
> news:memo.20050421130954.1752A@russellscott.btinternet.com...
>
>
|
|
|
|
|