TimeTrex Time and Attendance

The issue is that this person is not calculating overtime correctly. It is set for 40 hours a week in the policy. I am running Linux, PHP 5 and MySql (mysqlt): SET SESSION sql_mode='ansi' (mysqlt): SET SESSION time_zone='America/Detroit' (mysqlt): select session_id,user_id,ip_address,created_date,up...

Here is a screen shot


The continuous time is set to 2 hours. Also in the beginning shortly after I punched it it worked. when I went to punch out for lunch then it stopped and had the in option automatically.

Currently TT will not automatically set the In/Out option on the punch like it used to. Is there a reason for this and if so, is there an easy way to change it?

That was it.
Thank you again.

I saved the debug buffer. It is also happening to every employee. Debug Buffer ============================================================================ Memory Usage: 2899936 ---------------------------------------------------------------------------- DEBUG [155]: [Function](): URI: /interface/ti...

After looking at this a bit more closely it appears that the SQL query comes back with the punches for the week and then the TimeSheetFormatArrayByDate function takes care of formatting the array for being displayed on the timesheet. It appears as though the function is the problem of why the date i...

I am having difficulty with a punch appearing on the wrong date. Here is the offending query. select a.*, c.date_stamp as user_date_stamp, b.note as note from punch as a, punch_control as b, user_date as c, users as d where a.punch_control_id = b.id AND b.user_date_id = c.id AND c.user_id = d.id AND...

Thank you for all your help. I will do that.

Seems like it takes a day or 2. Is it possible it could be a permission issue? drwxrwx--x 2 apache apache 4096 Apr 2 12:15 02 drwxrwx--x 2 apache apache 4096 Apr 2 13:22 03 drwxrwx--x 2 apache apache 4096 Apr 2 12:16 09 drwxrwx--x 2 apache apache 4096 Apr 2 12:18 13 drwxrwx--x 2 apache apache 4096 A...

I still continue to get this. When I delete the tmp files it works fine for awhile then starts up again. Any insight? Should I set another cron job to remove the file automatically?

I had that problem and I had MySQL 5.0.24a, TimeTrex 1.5.1 and Linux 2.6.

Here is the thread.

http://forums.timetrex.com/viewtopic.php?t=149

This might help.

Thank you again. I didn't change the pay period because we only have 1 and it has never been changed. So from the start its been right. Now for the cache being deleted that worked. As soon as I removed it, it would allow me to change the Policy Group for the employee.

I have several employees setup in the TimeTrex and when I change the policy group I get an email saying the error below and get the wonderful maintenance screen after I hit submit. DEBUG [786] Array: <b>UserFactory::isUniqueEmployeeNumber()</b>: Unique Job Item: 59 <pre> string(2) "59" </p...

no. Ever since I removed the other cron job its been fine. The only emails I got were today which was the beginning of a new pay period. Not sure if the duplicate rows just caused that error.

I received an error message in my email. DEBUG [153]: <b>[Function]()</b>: URI: /interface/punch/EditPunch.php<br> DEBUG [155]: <b>[Function]()</b>: Production: 1<br> DEBUG [486]: <b>Authentication::Check()</b>: Session Name: SessionID<br> DEBUG [492]: <b>Authentication::Check()</b>: Session ID: fa2...

Thanx for the help. I will look into it.

But thats just it. I have changed the settings in timetrex.ini.php file. Thats why I am having trouble understanding why this might have been happening.

I guess now I am wondering why TimeTrex cron jobs don't notice the different database. I have go through and completely changed the settings for the 2nd Timetrex installation I have and yet when I disabled the cron job that seemed to take care of the problem. The 2nd timetrex installation is in a co...

You might be right on that. I did have 2 cron jobs working. I created a separate virtual host in apache so that I could modify TimeTrex without disturbing the original. I created a separate database and cron job. I did disable the cron job yesterday as a test and it did keep me from getting any erro...

I don't know if I could narrow it down but the error reports come in the morning. So my guess is that when everyone is punching in the morning. I am not sure how the user_date table is used so I can't give you much further detail. I have changed only 1 line in the source code and that was for gettin...

Do you want a mysqldump of the whole table? I could do that.

I did the mysql query
and it returned the same results.

Here is some more information. I ran a query to find duplicates and this is what I came up with. select count(*) as num , user_id, date_stamp from user_date group by date_stamp, user_id having count(*) > 1; "num","user_id","date_stamp" 2,2,"2007-03-03" 2,3,&qu...

I am gonna try to get you as much information as I can. Here is the error log I recieved this morning and I am sure more will come. DEBUG [155]: <b>[Function]()</b>: Production: 1<br> DEBUG [56]: <b>[Function]()</b>: 0. User: jefferya<br> DEBUG [192]: <b>UserDateFactory::findOrInsertUserDate()</b>: ...

Here is the status list. Its in Comma Delimited Format. "Name","Engine","Version","Row_format","Rows","Avg_row_length","Data_length","Max_data_length","Index_length","Data_free","Auto_increment&q...