--- fredbird67 <[EMAIL PROTECTED]> wrote: > I've tried messing with the field type for the time in the > database, such as timestamp vs. time vs. timedate, which yielded even > strangER results. For some reason, the timestamp seems to insist on > living in the not-too-distant past, as in last December and I can't > figure out why. It's not giving me an error message or anything, it's > just giving me any time (I even got the Unix epoch at one point, > imagine that!) EXCEPT the correct time. How do I correct this?
Just a quick comment. The first timestamp field will get updated to the current server date and time (make sure it's set correctly) each time the record is inserted or updated. The other datatype is datetime (not timedate) and will hold the value you enter until specifically changed. The second and later timestamps behave like datetime fields and do not change. Perhaps this will lead you to the solution you seek. James _____ James D. Keeline http://www.Keeline.com http://www.Keeline.com/articles http://Stratemeyer.org http://www.Keeline.com/TSCollection http://www.ITeachPHP.com -- Free Computer Classes: Linux, PHP, etc. Summer Semester Begins Jun 20 -- New Classes Start Every Few Weeks. Community email addresses: Post message: [email protected] Subscribe: [EMAIL PROTECTED] Unsubscribe: [EMAIL PROTECTED] List owner: [EMAIL PROTECTED] Shortcut URL to this page: http://groups.yahoo.com/group/php-list Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/php-list/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
