M
Mick
This is driving me crazy!! I have with the Jon’s help on a previous thread
tried to track it but no good as yet. I have put together a test site so all
can see what is happening.
I have a Database Interface Wizard for my Access database.
http://www.prstructuralglazing.com/_database1_interface/property_table/editor/login.asp
user = “a†password=â€aâ€
There is a date field called “datebookedon†default set to “Date()â€.
There is only one record in the test database, Record 1.
If I view the details, via the DIW ok.
If I go to edit, no problem.
As soon as I say ok (i.e. finished editing), all the date fields change to
US style, unless the number of the day is over 12 which wold make the change
a nonsense.
e.g. 08/09/2006 becomes 09/08/2006. but 26/08/2006 does not change.
If you then go to edit again, and just do a save the date switches back, and
will toggle every time you edit the record. As I am using this field to
calculate time since the record was entered, it throws out the whole system.
I thank you for your interest. Mick
tried to track it but no good as yet. I have put together a test site so all
can see what is happening.
I have a Database Interface Wizard for my Access database.
http://www.prstructuralglazing.com/_database1_interface/property_table/editor/login.asp
user = “a†password=â€aâ€
There is a date field called “datebookedon†default set to “Date()â€.
There is only one record in the test database, Record 1.
If I view the details, via the DIW ok.
If I go to edit, no problem.
As soon as I say ok (i.e. finished editing), all the date fields change to
US style, unless the number of the day is over 12 which wold make the change
a nonsense.
e.g. 08/09/2006 becomes 09/08/2006. but 26/08/2006 does not change.
If you then go to edit again, and just do a save the date switches back, and
will toggle every time you edit the record. As I am using this field to
calculate time since the record was entered, it throws out the whole system.
I thank you for your interest. Mick