Jim Dettman
jimdettman at earthlink.net
Sat Jun 5 13:45:10 CDT 2004
John, <<I have this db available for anyone who would like to look at this.>> Send it along. I'm curious. Jim (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of jwcolby Sent: Saturday, June 05, 2004 12:55 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Record locking bug Jim, In fact I updated my OfficeXP to the latest revision last night as I was testing this at home. I have SP3 installed on A2K. I thought there was an SP4 for A2K but I no longer see it out there so maybe they recalled it. John W. Colby www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Saturday, June 05, 2004 11:08 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Record locking bug John, Are you up to date on service packs? There were some problem with record level getting flipped on in the initial release. Jim (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of jwcolby Sent: Saturday, June 05, 2004 9:48 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Record locking bug >With the database window open, go to Tools;Options;Advanced and make >sure "Open databases using record level locking" is checked. Has always been set, still is. >Access will still use page locking when: >Bulk updates w/SQL. I am just manually editing (through a query) a single record in the case of this bug demo. >Updating memo fields. I intentionally deleted the only memo field in the table to ensure this wasn't it. That wasn't it. >Using ADO w/ lock granularity set to 1. Not using ADO, just manually editing the record through a query. >Updating indices. Hmmm... I am updating a FK field that of course has an index. I just removed the index on this field, saved the tables, and tried again, still getting the locking of surrounding records. John W. Colby www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Saturday, June 05, 2004 8:30 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Record locking bug Bob, Sorry for repeating what you said. Just goes to show that I need to take the time to read the entire thread before I stick my .02 in. Jim Dettman (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Bob Hall Sent: Friday, June 04, 2004 11:19 PM To: AccessD Subject: Re: [AccessD] Record locking bug On Fri, Jun 04, 2004 at 10:37:39PM -0400, jwcolby wrote: > I think I have stumbled on a record locking bug. With the database window open, go to Tools;Options;Advanced and make sure "Open databases using record level locking" is checked. Access will stil use page locking when: Bulk updates w/SQL. Updating indices. Updating memo fields. Using ADO w/ lock granularity set to 1. That's the obvious stuff. Hope it helps. Bob Hall -- _______________________________________________ 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 -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com