Charlotte Foust
cfoust at infostatsystems.com
Fri May 30 13:19:24 CDT 2008
John, If you're setting locks in ADO and editing the table in DAO, you will find differences. I ran into that a long time ago, but I've forgotten the details. I think that's why I was always so careful to limit myself to working in one model or the other at a time. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Friday, May 30, 2008 9:34 AM To: Access Developers discussion and problem solving Subject: [AccessD] Been Dazed and Confused for so long it's not true. OK, now that I have my test code running... I am locking all these records, and in the USER INTERFACE (open a table and click in a record) the record is locked. I cannot edit the memo IN THE TABLE. BUT my code opens a recordset and can edit that exact same record. If (from in the table) I click records / remove Filter/Sort the edit that I just performed in the recordset shows in the memo field AND the record is STILL LOCKED looking directly in the table - I still can't edit it through the table directly. I am using DAO recordsets to perform the edit. Is there a property that I am supposed to set to cause the DAO recordset object to honor the locks? To DAO records not see the locks? This is truly strange and not what I was expecting. -- John W. Colby www.ColbyConsulting.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com