Separate names with a comma.
Missed the live Ask the Expert event?
Not to worry. Check out the archived thread of the Q&A with Ken Hutcheson, President of U.S. Lawns, and the LawnSite community in the Franchising forum .
Discussion in 'Questions, Rules, Suggestions' started by Mikes Lawn Landscape, Oct 21, 2003.
On December 31,1969
There might be a problem
If your traveling down the road in a four wheel banana, and your left wing falls off, how many pancakes would it take to rebuild a doghouse?
Two and a half windows.
I feel like that duck on the commercial with Yogi Bera. uuuuuuuuuhhhhhhhhh?
Yes, I know, me too. I figured my post made as much sense or more than his.
I like my dec 31 1969 birthdate makes me feel younger
Here is my guess.
Lawnsite is on a unix based server. Unix based code bases all of there time on the number of seconds after January 1, 1970. This is called the Unix Epoch. When people do not enter a date for their birthday - it probaly registers that as 0 -- or one second before the epoch -- which would be December 31, 1969.
The code needs to be reworked so that this is seen as an empty data value and not as a zero data value.
Yeah, that's pretty much what I explained there: http://www.lawnsite.com/showthread.php?s=&threadid=54060
I will try to look into this soon, but fixing the duplicate post problem is a much higher priority for now.
mine is entered as april 28 but shows up as dec 31
Does it make sense now Elephant Nest ???
There was a bug with the date calculation when the date was prior to the Unix Epoch (Jan 1 1970). I have implemented a workaround for this, so the proper birthday is now shown.