Re: Sometimes can't save with Wizard's Save button

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: "Linq Adams via AccessMonster.com" <u28780@uwe>
Date: Fri, 21 Dec 2007 01:48:06 GMT

There's absolutely no reason to loop thru controls, simply to save a record
that has changed.You would only do this if you were runnng some kind of data
validation code, not simply to save all changed controls.

The two standard way of saving changing to a record are either

doCmd.RunCommand acCmdSaveRecord

or:

If Me.Dirty Then Me.Dirty = False

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200712/1

.

Follow-Ups:
- Re: Sometimes can't save with Wizard's Save button
  - From: Jordan
- Re: Sometimes can't save with Wizard's Save button
  - From: Jordan

References:
- Sometimes can't save with Wizard's Save button
  - From: Jordan
- Re: Sometimes can't save with Wizard's Save button
  - From: Minton M

Prev by Date: Re: Sometimes can't save with Wizard's Save button
Next by Date: Re: Applying Filter to Form in a Looping Macro Causes Catastrophic Err
Previous by thread: Re: Sometimes can't save with Wizard's Save button
Next by thread: Re: Sometimes can't save with Wizard's Save button
Index(es):
- Date
- Thread