standerdizing a date from calander - missmatch

[andre5]

Hi

I am using MSCAL.Calendar.7 as a calander to update a field in one of my forms. My problem is that it keeps switching my days (below 12) to months and the monthes ie August 4 2005 becomes 08 april 2005.

The form is used by multiple people and the regenal settings might be diffrent. Is there any other way to make sure that the date stays the same as entered?

Regards,
Andre

 

[Norie]

Andre

Try not to use the control.

Whenever you are developing anything that might be used across different versions/settings it's best to just use the standard controls.

How exactly are you using the control?

 

[andre5]

Hi

I have deleted the calender. and created a table with all the dates dd/mm/yyyy. If I formate as long date it has the 4th of Jan as the 4t of jan.
I created a combo box linked to this table but now if I pick 04/01/2005 it changes to 1 april 2005.

I must admit I am very confused now

 

[pritcham]

Hi

I think that this is due to Access (and many other DB systems) storing dates as mm/dd/yyyy - despite how they're displayed/formatted at the user interface level which would explain why 04/01/2005 (dd/mm/yyyy format) is being mistaken for 01/04/2005 (mm/dd/yyy format).

It might be a lot easier to store the dates in the format Access wants and just alter how they're displayed via the 'format' value of the controls.

Hope this helps
Martin

 

[andre5]

Thank you,
It looks like that is the only way to do it.

 

[Norie]

Andre

Could you please give more information on what you are doing?

If you are using date fields you should have no problem with system settings.

Martin

As far as I know Access/Excel actually store dates as integers.

For example, today 11th November 2005 is 38636.

 

[pritcham]

Hi Norie

Yes, you're right (of course) in how Access etc stores dates internally, but externally (i.e. when you query the field etc) I think that, regardless of your regional settings, it defaults to the American mm/dd/yyyy format meaning you need to either query using this format, or make the date you're querying with unambiguous (i.e. use 01/Apr/05 instead of 01/04/05 which could be mis-interpreted as Jan/04/05) - I know I had one or two surprising query results some time back that basically boiled down to this 'misunderstanding' of dates.

That (issue), of course, could have been down to me but I'm fairly sure I did some digging around at the time and that was the conclusion I came to.

Hope that helps
Martin