What you posted seems to function as you wanted.
What you posted seems to function as you wanted.
How did I know that was going to happen (your question) :-). We did not verify. Unfortunately we do not have another machine we can dedicate to this. Access 2007, as we understand it, only allows you to run one (1) instance of the program; if not, please enlighten us.
This issue we are discussing is intermittent; for the most part (recently noticed) will only occur after the program or machine has been idle or awakens from a sleep state; even then it is not guaranteed to happen each and every time.
Here is an example of our definition of intermittent:
From a fresh, newly created table, associated relationship(s) and forms, approximately fifty (50) records were entered before the first instance of this took place, 1/4/2012 4:40:55 AM, the second: 1/6/2012 12:36:00 AM, the third instance: 1/7/2012 1:02:55 AM, fourth: 1/9/2012 5:34:24 PM --there have been two (2) or three (3) more occurrences between 01/09/ and 01/14/2012.
That said, if you prefer we do a little more testing, at least to confirm what we sent you exhibits the same behavior, we can do that. It will just take us more time; given the above. :-) Please bear in mind, the live database that is in fact exhibiting this behavior has been changed (noted earlier). We disabled this (time-stamp) field at the form level (within the forms properties) and continue to use the following:
Private Sub DONE_Click()
Me!DATE_ENT = Now()
DoCmd.RunCommand acCmdSaveRecord
DoCmd.Requery
End Sub
No repeat occurrences of the problem (yet). It would still be very nice to know what is causing the issue in the first place. If the recent changes have rid us of the problem, we can only wonder, is there an issue with using, or the way the date-picker functions in conjunction with the above snippet.
As you know intermittent issues are sometimes impossible to track down as to the exact cause. I would go with your current scheme and see if the issue reoccurs.