By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,686 Members | 2,770 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,686 IT Pros & Developers. It's quick & easy.

Row-level locking Q. Front-end? Backend? Both?

P: n/a
(I've tried this Q in the ms forums without response. See how it goes
here.)

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 because that is my immediate interest
but obviously it could be continued
further)

Enlightenment welcomed.

Peter
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

From the Access Help article "RecordLocks Property" it appears that the
lock type only applies to the front-end. IOW, when the front-end
accesses the data it applies the indicated lock type; another front-end
would apply it's own lock type.

For the record :-) Access doesn't have true row (record) locking - it
has page locking. One page is 4Kbytes. Depending on the size of the
record, a page may contain more than one record.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQm1pHYechKqOuFEgEQKldACcCtyIb8n2neIZ8UnXVEm/ohYqVC0AoOOq
CXMbis8h+8hata6kHH15W4Cg
=z7QJ
-----END PGP SIGNATURE-----
Peter wrote:
(I've tried this Q in the ms forums without response. See how it goes
here.)

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 because that is my immediate interest
but obviously it could be continued
further)

Nov 13 '05 #2

P: n/a
Bri

MGFoster wrote:
For the record :-) Access doesn't have true row (record) locking - it
has page locking. One page is 4Kbytes. Depending on the size of the
record, a page may contain more than one record.


True for AC97 and earlier, optional for AC2K on.

--
Bri

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.