On Wed, Feb 8, 2012 at 5:32 PM, Dan Covill <dcov...@san.rr.com> wrote:

> On 02/08/12 09:45, Fred Taylor wrote:
> > We're discussing the options this afternoon.  But as with all things in
> the
> > programming world, the fix is needed yesterday!
> >
> > All the clever ideas were immediately trashed soon after their
> suggestion.
> >   Some of those were even my ideas!<g>
> >
> > Fred
>
> Hi, Fred
>
> I was in a meeting once when a VP asked me when we would have a change
> made.  I said something like 'two weeks'.  He said "That's not good
> enough, we have to have it next week."  I said "You can say that, and I
> can even agree to it, but it still won't happen."
>
> I'm with Ed, any solution has to start with saving the UTC.  And don't
> use the current time field - add a new UTIME and convert.
>
> And, when pushed, ask the pushers if they want the problem solved or not?
>
> Dan


 No worries Dan, we're going the UTC route in a new field in the tables
affected.  There's only a few tables that will require this, but still
plenty of changes to be made in lots of places.

It'll be done when it's done, and not one minute before.

Fred


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/cajcbksp0jvugr1wlt5o2h_p-omj6ag7ztq2ddtv+0tpt9g2...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to