My computer vs Her computer

[BillR]

I have a rather large access application that inputs, stores and tracks, etc. a lot of dates. One user has a problem with various dates in her tables showing up 12/31/1899. I cannot make the system do it on my computer. I have tried adding and removing input masks, formats, traps etc. to no avail. Every time I think I have eliminated the problem, she calls me back to report it has returned (usually not immediately). These dates are user entered via bound and unbound text boxes - some by VB code. I have isolated the occurance to one or two fields in that many tables. Any ideas?

 

[Rich]

Check the regional settings on her computer and that your date fields are actually defined as date/time fields and not long integers, text etc. I,ve seen this where the field has been defined as long integer and the default value is left at 0.
HTH

 

[BillR]

Thanks Rich! I found 1 hidden text box that could come into play if user tried to enter null or "" date. It had an input mask instead of short date format. It could update dates from a multi-select list box - meaning it could corrupt many dates with 1 click of the button! All others are good. Ill send the app to her and have her check her regional setting(s).