Max Wanadoo
max.wanadoo at gmail.com
Fri Mar 6 00:11:01 CST 2009
> unless you first open a recordset in ADO. Do you mean ANY recordset from the BE or the specific recordset that you want to open in DAO must be opened in ADO then closed and re-opened inDAO? Strange? Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: 06 March 2009 00:58 To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Page Locking Happening - But Set to Record Locking 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 -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com