[AccessD] Page Locking Happening - But Set to Record Locking

jwcolby jwcolby at colbyconsulting.com
Thu Mar 5 19:21:12 CST 2009


 >   There is also a bug where DAO in code will not record level lock unless you first open a 
recordset in ADO.  There is a MSKB article on that which I can dig out if you want.

Wow.  That is the first I have ever heard of that one.  The things you learn on this list.

John W. Colby
www.ColbyConsulting.com


Jim Dettman wrote:
> Dan,
> 
>   Even though you are set for "record level" locking, not all operations are
> done at that level.  Index updates, memo pages, DML operations, etc. are
> always done at page level.
> 
>   Also the first user in must be set for record level locking otherwise
> everyone defaults to page level regardless of setting.
> 
>   There is also a bug where DAO in code will not record level lock unless
> you first open a recordset in ADO.  There is a MSKB article on that which I
> can dig out if you want.
> 
> Jim. 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
> Sent: Thursday, March 05, 2009 6:11 PM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Page Locking Happening - But Set to Record Locking
> 
> Twice now I've seen what appears to be page locking in the BE mdb when that
> file is set to record locking.  About 8 contiguous records show locking -
> reminds me of Access 97, but they are using Access 2000.
> 
> Has anyone seen this before or know of a fix?
> 
> Thanks!
> Dan
> 
> 
> 
> 
> 



More information about the AccessD mailing list