[AccessD] Access error 2101

Doug Murphy dw-murphy at cox.net
Tue Sep 22 19:04:37 CDT 2009


Hi Rocky,

I can try that but I really would like to know the fundamental cause of the
problem since I use me.dirty=false in all my apps. It will be informative to
see if I get the error or another by using another save methode. The funny
thing is that the record is saved, because I go off the form when it is
closed I guess.

Thanks for you thoughts.

Doug

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Tuesday, September 22, 2009 5:00 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access error 2101

Doug:

Not sure why you would get that but would DoCmd.RunCommand acCmdSaveRecord
work?  Or Me.Refresh?

Rocky
  

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: Tuesday, September 22, 2009 3: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




More information about the AccessD mailing list