Mark Boyd
MarkBoyd at McBeeAssociates.com
Tue Nov 18 11:57:05 CST 2003
Liz - Thanks for the input. I searched the table, but didn't find corrupt records. Thanks, Mark -----Original Message----- From: Liz Doering [mailto:liz at symphonyinfo.com] Sent: Tuesday, November 18, 2003 11:36 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] acNewRec Mark, Have you checked for a corrupt record in the affected tables? It will usually show up with ####### in one field. Deleting the record clears up the mess. Liz Doering Symphony Information Services liz at symphonyinfo.com www.symphonyinfo.com 763-391-7400 -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Boyd Sent: Tuesday, November 18, 2003 10:03 AM To: AccessD at databaseadvisors.com Subject: [AccessD] acNewRec I have an Access2002 mdb that is being used by 5 users. The front-end is located on each user's hard drive, while the linked tables are located in an Access2002 mdb on the network. There haven't been any problems in the past month, but now users are receiving the following error when adding a new record to a form: "Could not update. Currently locked". The code is "DoCmd.GoToRecord, , acNewRec". Any ideas? TIA, Mark Boyd Sr. Systems Analyst McBee Associates, Inc. _______________________________________________ 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