Re: New record not updating when the form is closed

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

This is a known bug in Access. Before using DoCmd.Close you have to force the
record to be saved, else if required fields are empty the record will simply
be dumped without any warning.

If Me. Dirty Then Me.Dirty = False
DoCmd.Close

--
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-modules/200802/1

.

Relevant Pages

  • Microsofts Answer to DoCmd.Close Bug
    ... I was looking in on answer a question without you guys help, SHAME ON ME!!! ... I discovered the bug where, using the close button DoCmd.Close, does not save ... says to use this code to check if one of your required fields is empty. ...
    (microsoft.public.access.forms)
  • Re: Solaris 10 - routing problems?
    ... That sounds like a bug. ... Those don't look like error messages. ... That's a usage error (need NAT), ... ipf.conf is empty, there is no traffic blocking at all. ...
    (comp.unix.solaris)
  • Re: Index 1 is out of bounds
    ... Yes, that does look like a bug but, as Bruno said, I think that most ... The instance is initially empty (i.e.it reports 0 ... The code you quoted creates a new OrderedCollection (in the ...
    (comp.lang.smalltalk.dolphin)
  • Re: Bug in Word 2002
    ... You expect an empty line between the two, ... not a terrible bug IMO, ... If you push Enter a second ... the cursor does advance to the next line. ...
    (microsoft.public.word.application.errors)
  • Re: tip: bzip2/lzma now in tip:x86/setup-lzma
    ... Fix a bug in gen_initramfs_list.sh: in case of failure, ... indeed an empty output file behind, ... testing it with the problem .config, on the problem test-system. ...
    (Linux-Kernel)