Help to confirm if a bug (or not)
We need help to confirm whether what is described herein is a bug, or something that we are doing incorrectly. If it is a bug, please report as needed. In either case please help us with a resolution without using a lot of VBA which we have not yet learned.
Short version: (yeah right)
Two separate forms for their respective (separate) tables; not related. Each have their own timestamp field/column with different names. Using the following snippet, one (1) of these forms works flawlessly, while the other (form) exhibits intermittent behavior. After the database remains open and idle, and/or, if the machine goes to sleep (not hibernate) then awakens -- attempting to enter a new record using the problematic form, associated table or code, the AFTER_UPDATE() or the DONE_CLICK() -- will not initiate/execute the "Me!DATE_ENT = Now()" <-- after we use the date picker then move to the next field, or single left-click the button-control .
Private Sub DATE_ENT_AfterUpdate()
Me!DATE_ENT = Now()
DoCmd.RunCommand acCmdSaveRecord
DoCmd.Requery
End Sub
Private Sub DONE_Click()
End Sub
NOTE: we have used the above code in AfterUpdate() or in DONE_Click with the same ill (intermittent) results.
The above code works flawlessly in either of the above events on 'form-1' and intermittently, regardless of what event, on the other 'form-2'; as previously stated.
This next description appears to be associated with the above, however you cannot see it while it happens, it takes place behind the scenes:
· Access has been open and machine idle; playing movies for approximately four (4) hours or more.
· Time to use access and enter a record. Once at the timestamp field, the user chooses 'today' from the date-picker (m/dd/yyyy), then uses the <tab-key> or mouse-click away from the field -- and the above "Me!DATE_ENT = Now()" does not execute within the field it is assigned to; leaving the user to think the code is broken.
After further review, we find that 'Access 2007' appears to have placed the results of "Me!DATE_ENT = Now()" in the immediate previous record for the same field, deleting the timestamp that was originally there; all the while the newly created record was entered correctly minus the results of " Me!DATE_ENT = Now()" which as stated earlier went to a previous records timestamp.
I don't see how we could have made a user error on this, given that we are using the same code within different form and this only happens with form-1.datefield and its associated table.datefield and not form-2. etc, etc.
Please help us to confirm, if at all, this is a 'BUG' or if in fact we have done something incorrect. When explaining please proceed slowly.
Thank you all for reading.