TimeStamp not being captured consistently "gmaccess2" <u24365[ at ]uwe> 21.07.2006 18:50:27 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

Re: TimeStamp not being captured consistently "Jeff Boyce" <nonsense[ at ]nonsense.com> 21.07.2006 18:59:24 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 "gmaccess2" <u24365[ at ]uwe> wrote in message news:63970b9b00119[ at ]uwe... [Quoted Text] >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

RE: TimeStamp not being captured consistently KARL DEWEY 21.07.2006 19:04:02 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. "gmaccess2" wrote: [Quoted Text] > 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 >