Real time database question

[joet5402]

I have created a database that tracks work orders in real time (whereas command buttons were created and when clicked displayed the current date/time), but I have a problem I've been unable to solve, and I'll try to provide as many details as I can (and I have attached the form view [doc6] and the form in design view [doc7]for reference: when I press the ‘call received’ command button, nothing appeared in the date field, but when I scrolled back then forward, the date appeared. Is there any reason for this happening? If you could leave a detailed answer, I'd greatly appreciate it; I am not super tech literate, so the answer in its simplest form is greatly appreciated.

Thanks again to whomever can help me
Joe

[RuralGuy]

What code or macro do you have behind the call received button?

[joet5402]

What code or macro do you have behind the call received button?

The macro I have is the following:

Action: SetValue

Item: [DATEREQUESTED]
Expression: Date ()

Not sure if that helps any.

[RuralGuy]

I was afraid you were going to be using a macro. Not my strong suit! Change the name of the control that is bound to the [DATEREQUESTED] field to something like txtDateRequested and then modify the macro so that you are setting the Control to Date() and not the field directly.

[joet5402]

I was afraid you were going to be using a macro. Not my strong suit! Change the name of the control that is bound to the [DATEREQUESTED] field to something like txtDateRequested and then modify the macro so that you are setting the Control to Date() and not the field directly.

Now when you say the "name of the control", do you mean the NAME part or the CONTROL SOURCE?

[RuralGuy]

If you renamed the control to txtDateRequested as suggested then your macro will SetValue of txtDateRequested and not [DATEREQUESTED].

[joet5402]

If you renamed the control to txtDateRequested as suggested then your macro will SetValue of txtDateRequested and not [DATEREQUESTED].

Nice, it worked...now I'm having the same problem with the Completion Date command button (End Date field); I had it working before, that's the weird part.

[RuralGuy]

The default name for a control is the name of the field to which it is bound. Unfortunately, when you use the name, Access does not know if you mean the control or the field, since it can get to either. As a result, I usually rename the controls in some form of naming convention.