Registered: June 2, 2007 | Posts: 4 |
| Posted: | | | | Hi,
I have noticed that although in the General Info section the Purchased Date is displayed correctly for my PC and Europe with DD/MM/YYYY, when I export the date is stored in the format YYYY/MM/DD.
Does anyone know a way to change this as it then unreadable in the application that I want to import it into.
Thanks,
Dave |
|
Registered: March 14, 2007 | Posts: 630 |
| Posted: | | | | I don't think you can change it unfortunately. The export should have been in the format YYYY-MM-DD, then all applications should read it correctly (those that doesn't are simply broken). | | | Regards Lars |
|
Registered: March 13, 2007 | Reputation: | Posts: 2,005 |
| Posted: | | | | Quoting yatesd2404: Quote: Hi,
I have noticed that although in the General Info section the Purchased Date is displayed correctly for my PC and Europe with DD/MM/YYYY, when I export the date is stored in the format YYYY/MM/DD.
Does anyone know a way to change this as it then unreadable in the application that I want to import it into.
Thanks,
Dave The export uses the standardized date format. To use something else would be really bad, because then the XML cannot be used on operating systems which has another date format than the PC you created the XML on (it would loose its purpose as a data exchange format). It is the job of the other application to convert it to the format it needs the date (which is a simple operation). You have 3 options: 1) The author of the other application fixes the import 2) You change the XML yourself (e.g. with a script which parses the XML and changes the values) 3) (I do not know if this will work. Depends on the other application): You temporarily set your system's setting to YYYY/MM/DD. But I think the problem is more, that the other application cannot handle the ISO date format, no matter which system setting is set. | | |
| | | Last edited: by TomGaines |
|
Registered: June 2, 2007 | Posts: 4 |
| Posted: | | | | Thanks for the replies, you were right it was actually a problem in the importing App which used a non XML Standard format.
They have now resolved this issue and everything works as expected.
Thanks,
Dave |
|