Correctly stored dates displaying as 12/30/1899 in forms

Hello Everyone,

I have a MS Access front end application with a form that displays
various dates with a linked table for the record source. These dates
are stored in a table called Bookings in Short Date format. The table
has a unique key called BookingNo. Users have the front end
application on their computer (PTS.MDB) and all the tables are linked
to a back end Access DB that sits on the server (PTS_BE.MDB).

For example we have the following date fields:
BookDate
ArriveDate
ManifestDate
FlightDate

There is no default value for a "booking" for those various fields.
However, people enter that data in a form, thus it's stored to the
table. When I open the table the values are correct:

BookingNo 377844
BookDate 07/19/2006
ArriveDate 07/20/2006
ManifestDate 07/20/2006
FlightDate 07/22/2006

When users open the form to look at the data however, they see:

BookingNo 377844
BookDate 12/30/2006 12:00:00 AM
ArriveDate 12/30/2006 12:00:00 AM
ManifestDate 12/30/2006 12:00:00 AM
FlightDate 12/30/2006 12:00:00 AM

When I left the office last night it was working correctly (or I'm sure
someone would have come to me complaining about it). I came into the
office this morning to find this happening. Nothing has changed in the
system since last night and this morning in terms of programming. I've
checked the system and the form's textbox formatting is still set to
display the correct record source (so the ManifestDate textbox has
ManifestDate as it's record source) and show the data in Short Date.
The record source for the form is still set to Bookings. I know that
some people have had this problem when they accidently overload system
defined functions such as Now(), or when information is being passed
between different database types, such as a stored procedure in SQL
server back end database passing dates to an Access front end
application, but this is not the case for this problem.

Has anyone else run into this, and does someone have a solution? I'm
at a loss here.

Thanks,
Elisabeth

Have you looked at the regional setting on the machine having the problem? It
could be that someone has changed the date settings.
--
Bill Mosca


"kolalakitty" wrote:

Hello Everyone,

I have a MS Access front end application with a form that displays
various dates with a linked table for the record source. These dates
are stored in a table called Bookings in Short Date format. The table
has a unique key called BookingNo. Users have the front end
application on their computer (PTS.MDB) and all the tables are linked
to a back end Access DB that sits on the server (PTS_BE.MDB).

For example we have the following date fields:
BookDate
ArriveDate
ManifestDate
FlightDate

There is no default value for a "booking" for those various fields.
However, people enter that data in a form, thus it's stored to the
table. When I open the table the values are correct:

BookingNo 377844
BookDate 07/19/2006
ArriveDate 07/20/2006
ManifestDate 07/20/2006
FlightDate 07/22/2006

When users open the form to look at the data however, they see:

BookingNo 377844
BookDate 12/30/2006 12:00:00 AM
ArriveDate 12/30/2006 12:00:00 AM
ManifestDate 12/30/2006 12:00:00 AM
FlightDate 12/30/2006 12:00:00 AM

When I left the office last night it was working correctly (or I'm sure
someone would have come to me complaining about it). I came into the
office this morning to find this happening. Nothing has changed in the
system since last night and this morning in terms of programming. I've
checked the system and the form's textbox formatting is still set to
display the correct record source (so the ManifestDate textbox has
ManifestDate as it's record source) and show the data in Short Date.
The record source for the form is still set to Bookings. I know that
some people have had this problem when they accidently overload system
defined functions such as Now(), or when information is being passed
between different database types, such as a stored procedure in SQL
server back end database passing dates to an Access front end
application, but this is not the case for this problem.

Has anyone else run into this, and does someone have a solution? I'm
at a loss here.

Thanks,
Elisabeth