Verify that you get midnight Jan 1, 1 AD from the following and you'll have the epoch adjustment value:
new Date( -62135596800000 ).toUTCString() Converting from timeticks returned by your webservice: var epochAdjustment: Number = -62135596800000; var d: Date = new Date ( CurrentTimeTicks / 10000 + epochAdjustment ); trace( d.toString() ); // client's local time --- In flexcoders@yahoogroups.com, "Mark" <[EMAIL PROTECTED]> wrote: > > I agree with you 100% Josh but the better ones want the all might $$ > and my company isn't willing to pay for it, it's just nice to have. > So I need to find a free one or give it up. But I'm not willing to > do that just yet... soon, but not yet. :-) > > They do have have some pseudocode on the site but it really shows it > using the DateTime in .Net. And my understanding of that is that's > built in so there's no convesions (although I could be wrong). > > -M > > > --- In flexcoders@yahoogroups.com, "Josh McDonald" <dznuts@> > wrote: > > > > Switch to a different web service, or call whoever provides it and > get some > > documentation :) > > > > What the hell is 1AD? We haven't been keeping nice records since > like 200AD > > or something. > > > > And do they count all the various leap seconds? What about that > time when > > some pope rejigged the calendar and we disappeared like 13 days or > > something? > > > > Anybody proving information of such a monstrously non-standard > fashion > > should also be providing some serious documentation and/or > pseudocode. > > > > -Josh > > > > -- > > "Therefore, send not to know For whom the bell tolls. It tolls for > thee." > > > > :: Josh 'G-Funk' McDonald > > :: 0437 221 380 :: josh@ > > >
