TimeStamp not being captured consistently

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

gmaccess2 - 21 Jul 2006 19:50 GMT

I have a split dB rolled out within my POB. Areas of the business have their
own forms to input data which is then captured in a main table on the backend.
One of the data fields I am capturing is a time stamp by using Date(). Out of
about 100 users, about 10-15% do not populate the backend table with the
timestamp. Their PC clocks are enabled and functioning correctly. Would
anyone know why it works for the majority and not for some? NOTE: I have not
tried NOW() guessing that the same thing would happen. Thanks in advance! GM

Reply to this Message

Jeff Boyce - 21 Jul 2006 19:59 GMT

You have a Date stamp if you are using Date(). If you need a date/time
stamp, use Now().

Regards

Jeff Boyce
Microsoft Office/Access MVP

>I have a split dB rolled out within my POB. Areas of the business have
>their
[quoted text clipped - 8 lines]
> tried NOW() guessing that the same thing would happen. Thanks in advance!
> GM

Reply to this Message

KARL DEWEY - 21 Jul 2006 20:04 GMT

How are you capturing is a time stamp? Is it a default of the table field,
default of filed in the form, or an event? The easiest would be a default of
the table field.

> I have a split dB rolled out within my POB. Areas of the business have their
> own forms to input data which is then captured in a main table on the backend.
[quoted text clipped - 3 lines]
> anyone know why it works for the majority and not for some? NOTE: I have not
> tried NOW() guessing that the same thing would happen. Thanks in advance! GM

Reply to this Message