[AccessD] Odd Form Behavior

I think of all the questions I asked, only the one about VBA code was worth
worrying about. I had misread another post online which had to do with
back-end freezing (this seems more like a front end issue). Anyway, here was
what I read:

http://bytes.com/topic/access/answers/828312-access-back-end-sometimes-freez
es


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Sunday, December 25, 2011 6:24 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Odd Form Behavior

No luck there.  Actually it was behaving badly before I put the save and on
dirty events in.  Gotta start deleting code and see what fixes it.

R
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Sunday, December 25, 2011 2:50 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Odd Form Behavior

It sounds like it is going into a loop because you are trying to do another
save during a save.

What happens if you  get rid of the OnDirty event and  change the  Save
button event to:

If Me.Dirty Then Me.Dirty = False

--
Stuart


On 25 Dec 2011 at 10:10, Rocky Smolin wrote:

> Dear List:
>  
> I have a form in an Access 2003 app exhibiting some odd behavior.  The
form
> is bound to one table.  When anything on the form is changed, the form
seems
> to lock - that is, you cannot move to another record using the navigation
> buttons.  Before making a change, the navigation buttons work.
>  
> I put a 'Save' button on the form with the one line in the click event
> DoCmd.RunCommand acCmdSaveRecord which generates the unhelpful error 'Run
> Time Error 2501 - The RunCommand action was canceled.'
>  
> If I put 'DoCmd.RunCommand acCmdSaveRecord' in the dirty event, it saves
the
> record but the navigation buttons are still not functional and I can't go
to
> design view.
>  
> Further, clicking 'View' and 'Design View' does not work at this point. I
> have to click the 'Exit' command button on the form or File-->Close. If I
> use the close button of the form I get a message "You can't save this
record
> at this time." although the record was saved because I added
> 'DoCmd.RunCommand acCmdSaveRecord' to the dirty event.
>  
> To eliminate the possibility that my installation of Access on this
machine
> got hosed, I moves the app and back end to a second machine and got the
same
> results. 
>  
> I would prefer not to use the save on the dirty event because I have an
undo
> button that the user likes.  But I think if someone can lead me a solution
> of the navigation button thing, this will solve the save problem.
>  
> Any ideas?  I'm stumped.
>  
> MTIA
>  
> Rocky Smolin
> Beach Access Software
> 858-259-4334
> www.bchacc.com <http://www.bchacc.com/> 
> www.e-z-mrp.com <http://www.e-z-mrp.com/> 
> Skype: rocky.smolin
>  
>  
>  
>  
>  
>  
> -- 
> 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