[AccessD] Access error 2101

Max Wanadoo max.wanadoo at gmail.com
Wed Sep 23 11:58:57 CDT 2009


Well, thanks for the feedback Doug.
My pet hate is when you TRY to help somebody and the only feedback is
another problem.


Aka DALE!

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: 23 September 2009 17:51
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access error 2101

Thanks for the link and reference. I had a bone head action in the forms
after update event that set the last modified date that was causing the
problem. The error message wasn't very helpfull in tracking this down, but
Allen's article made me look. Moved my set last modified date and all is
well.

Thanks again. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jack and Pat
Sent: Wednesday, September 23, 2009 8:20 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access error 2101

Doug,

I found this by Allen Browne  -- may be helpful....

 

http://www.eggheadcafe.com/conversation.aspx?messageid=31895796
<http://www.eggheadcafe.com/conversation.aspx?messageid=31895796&threadid=31
895722> &threadid=31895722

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: Wednesday, September 23, 2009 9:28 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access error 2101

 

This is the way it is being done now. I just didn't put the whole routine

in. 

 

-----Original Message-----

From: accessd-bounces at databaseadvisors.com

[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters

Sent: Tuesday, September 22, 2009 5:20 PM

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

 

-- 

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




More information about the AccessD mailing list