Access silently loses the entry if you use the Close action/method at a time
when the record cannot be saved for any reason (e.g. duplicate index,
required field missing, validation rule not met, ...)
Details:
http://allenbrowne.com/bug-01.html
The other scenario that causes people to believe records are lost (though
they are not) is if you do not set the Required property of foreign key
fields. This correctly saves the record with a null foreign key, but if the
record was in a subform, it matches none of the records in the main form,
and so it never shows up again in the subform.
Details in "Error 3" of this article:
http://allenbrowne.com/casu-12.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Cillies" <lee@prologic.ie> wrote in message
news:ba262325.0405040338.18d687c0@posting.google.c om...[color=blue]
> Hello all,
> I was recently browsing the forum and remembered seeing a message
> relating to MS Access Bugs/Flaws. The thing is I cannot find that
> thread anymore, and so was wondering does anyone know if MS Access
> (97-2000) has a bug in it where the user thinks the application is
> saving a record where in fact the record has not been saved.
>
> The reason I am asking is that this problem has now arrisen with a DB
> I have built, where the end user has contacting me stating that a lot
> of records are missing that where deffiently entered.
>
> kindest Regards[/color]
NS Access Saving Bugs 
