Set Default Date to European Format without changing Regional settingof the PC

[Booli]

Dear All

I tried several times to set the data type as Date/Time in DD/MM/YYYY
(European Format) in a table design view.
My Regional settings is US format.
Is there any way to set the date as 31/11/2010 (DD/MM/YYYY) in my
table without changing the Regional setting of the PC.
Any help is appreciable

regards
Lasitha

 

[John Spencer]

The best you can do is set the FORMAT property to "dd/mm/yyyy". The date will
display in that format. However, you are still going to be forced to enter
the date values in mm/dd/yyyy format or in yyyy-mm-dd format in order to end
up storing the desired date.




John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

 

[Douglas J Steele]

Not sure that's 100% true, John: the CDate function respects regional
settings, so you might be able to get away with wrapping input fields with a
call to that function.

"John Spencer" wrote in message

However, you are still going to be forced to enter
the date values in mm/dd/yyyy format or in yyyy-mm-dd format in order to end
up storing the desired date.




John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

 

[John Spencer]

Yes, but the poster said he did not want to change the regional settings from
US settings. If the poster can change the regional settings then it would
probably not be necessary to force the view of the date using the format property.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

 

[David-W-Fenton]

the CDate function respects regional
settings, so you might be able to get away with wrapping input
fields with a call to that function.

Hmm. Doesn't CDate() return the actual stored date value, but the
results are displayed as the text representation of the date, based
on regional settings? That is, the help file says that CDate()
returns a date data type, which means it's a 64-bit number
(according to the help file's definition of the date data type).
What displays is the text representation of that date, the format of
which is determined by the regional settings.

 

[Douglas J Steele]

I read that as meaning that if User A has his Date set to dd/mm/yyyy in
Regional Settings, and User B has her Date set to mm/dd/yyyy, then it'll
work user CDate([Input Date Value]) for either.

"David-W-Fenton" wrote in message

the CDate function respects regional
settings, so you might be able to get away with wrapping input
fields with a call to that function.

Hmm. Doesn't CDate() return the actual stored date value, but the
results are displayed as the text representation of the date, based
on regional settings? That is, the help file says that CDate()
returns a date data type, which means it's a 64-bit number
(according to the help file's definition of the date data type).
What displays is the text representation of that date, the format of
which is determined by the regional settings.

 

[David-W-Fenton]

I read that as meaning that if User A has his Date set to
dd/mm/yyyy in Regional Settings, and User B has her Date set to
mm/dd/yyyy, then it'll work user CDate([Input Date Value]) for
either.

But my point is that it entirely depends on what you're doing with
the results. Access formats the result according to your regional
settings, but CDate() isn't *returning* the result according to
them. It doesn't return a text representation of the date, but an
actual date value. In most contexts, Access will present that as a
text representation according to the regional settings.

To me, it's an important distinction.