Total Hours include previous months... Pay Period = None
Posted: Thu Jan 07, 2010 8:26 pm
Hi,
This post relates to forum post http://forums.timetrex.com/viewtopic.php?f=2&t=669
but that post seemed a bit different, more complicated, and didn't provide me with an answer, so I'll start a new topic...
We were using TimeTrex 2.2.8 successfully from May 2008 through October 2009. Novermer 2009 seemed normal, but was actually the beginning of an undefined pay period. This became obvious in December 2009, when the Total Hours shown on timesheets did not start from zero for the month, but instead kept adding to the November hours.
After some help from Shaun, we were able to upgrade from 2.2.8 to 3.0.4 (see http://forums.timetrex.com/viewtopic.php?f=1&t=1561). We ran the standard automatic installation on a Fedora Core 8 linux box with PHP 5, using the postgresql that comes with TimeTrex. We then restored our old data.
However, the Pay Period issue still remains. The top-referenced post seems to imply that the problem may fix itself in a few days?? Is this true??
When I log in and go to the Pay Period List, it looks like this:
1 Monthly Monthly N/A 01-Nov-09 12:00 AM 30-Nov-09 11:59 PM 01-Dec-09 12:00 PM
2 Monthly Monthly OPEN 01-Oct-09 12:00 AM 31-Oct-09 11:59 PM 31-Oct-09 11:59 PM [ View ] [ Edit ]
What should I do to properly define November 2009, December 2009, January 2010, and to have all future periods defined automatically?
Thanks,
Andrew
This post relates to forum post http://forums.timetrex.com/viewtopic.php?f=2&t=669
but that post seemed a bit different, more complicated, and didn't provide me with an answer, so I'll start a new topic...
We were using TimeTrex 2.2.8 successfully from May 2008 through October 2009. Novermer 2009 seemed normal, but was actually the beginning of an undefined pay period. This became obvious in December 2009, when the Total Hours shown on timesheets did not start from zero for the month, but instead kept adding to the November hours.
After some help from Shaun, we were able to upgrade from 2.2.8 to 3.0.4 (see http://forums.timetrex.com/viewtopic.php?f=1&t=1561). We ran the standard automatic installation on a Fedora Core 8 linux box with PHP 5, using the postgresql that comes with TimeTrex. We then restored our old data.
However, the Pay Period issue still remains. The top-referenced post seems to imply that the problem may fix itself in a few days?? Is this true??
When I log in and go to the Pay Period List, it looks like this:
1 Monthly Monthly N/A 01-Nov-09 12:00 AM 30-Nov-09 11:59 PM 01-Dec-09 12:00 PM
2 Monthly Monthly OPEN 01-Oct-09 12:00 AM 31-Oct-09 11:59 PM 31-Oct-09 11:59 PM [ View ] [ Edit ]
What should I do to properly define November 2009, December 2009, January 2010, and to have all future periods defined automatically?
Thanks,
Andrew