Currently this happens yes? i input 12-12-2006 18:00 (My Time) and it gets parsed on the server (in your location -9 hours) and stored like that.
when you timezone it it will be converted and stored like 12-12-2006 09:00 (your time) when i read it back in its gets converted again so i see 12-12-2006 18:00 you read it in and you see 12-12-2006 09:00 Thats fine for appointments but i don't want to have it everytime. sometimes the data i type in is really that date (its a literal) Example on a website: Event: Servoy World location: Amsterdam from: 12-12-2006 09:00 to: 13-12-2006 18:00 Then the time CAN'T be converted.. Because i already stamp in by giving a location. Because if you look at that info then you should see exactly the same output then when i look at it. No matter where you are. also: "2) The first nasty thing is that pulling 12/12 through a date form, will give you a date initialized with 12/12 *but also with all time fields zero-d out*." Do you mean that you had a date (filled in with complete time) and then you format it like 12/12 and then convert it back you loose everything except the 12/12 that you entered? I have a solution for that i have a Stable DateConverter that works by setting the original value then apply the string that you want to parse and only the fields that are in that string are set the rest is kept as it was. johan
