[AccessD] 2001 Error - You cancelled the previous operation

ROTFL.  So true, like C#.

John W. Colby
Colby Consulting

On 10/3/2011 9:04 AM, Jim Dettman wrote:
> <<I always use unbound controls, and validate
> field by field, and then use SQL and refresh the form...>>
>
>    Why are you bothering to use Access then?  If your going to go through all
> that work, you might as well use something else that gives you more features
> and capabilities.
>
> Jim.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Benson
> (VBACreations.Com)
> Sent: Monday, October 03, 2011 12:31 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] 2001 Error - You cancelled the previous operation
>
> I never let Access Add New, I always use unbound controls, and validate
> field by field, and then use SQL and refresh the form... and I don't have
> these problems  ;-)
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
> Sent: Monday, October 03, 2011 12:23 AM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] 2001 Error - You cancelled the previous operation
>
> After hours and hours of testing this, I came to the conclusion that unless
> I trap the vbKeyEscape in the KeyDown event handler, I am unable to add a
> new record to a form after an undo has occurred. I get this dreaded 2001
> error which appears to be a misleading one.
>
>
>
> It appears that an UnDo condition throws the form into a tizzy-state. Any
> method of attempting to add a new record after an undo has occurred either
> with a RunCommand GotoRecord acNewrec directive or trying to do an AddNew
> and Bookmark ... all fail. When I kill the escape key, all is well..but of
> course, my users are mad.they cannot undo the record.
>
>
>
> Unless I'm missing something , this is definitely a bug, no ?
>