Max Wanadoo
max.wanadoo at gmail.com
Wed Sep 23 03:16:05 CDT 2009
Dan, is that error being trapped? Is so comment out the On Error line and see where the actual error is being found. My *guess* is that the error line is elsewhere and not being *discovered* until you try to save it. Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: 23 September 2009 01:20 To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Access error 2101 Long shot - but perhaps: If Me.Dirty = True then Me.Dirty = False HTH! Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy Sent: Tuesday, September 22, 2009 5:58 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Access error 2101 Folks, I have an Access 2007 application that has developed a problem in a relatively simple data entry form. When a record is created or edited I have a save button that uses Me.Dirty = False to explicitly save the record or changes. I now get an error on this line saying "Error 2101 (The setting you entered isn't valid for this property.)" This is new to me as I use this method all the time. Can anyone on the list give me any insight into what might be causing this. Thanks in advance. Doug -- 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