Closing TimeClockWindow

[undnyc]

Is there anyway to have the software close instead of minimizing? I ask this is because sometimes the software runs in the background and people cannot tell if they punched in or not. Currently the only fix for that is to close the program and restart.

Thank you.

[Paul Mayer]

Anyone can tell if they are punched in. The green flag in the Employee interface shows that they are punched in, if that are not punched in it is red. See this Video:

http://zpay.com/help/tcwhelp/Clock-in.htm

[undnyc]

Im having a problem running over the network. When program stays open for a while and employee try's to punch out, it wont punch them out properly. Best way to fix this kind of problem is to completely shut down TimeClockWindow and restart then employee could punch out.

[Paul Mayer]

Does the employee get a pop up message telling them the time changed and they need to contact the administrator to enter your password? Or is it something else? Generally TimeClockWindow will pop up a Bug Report tool and if you do not use that to report the problem supplying your name and email address and tell us what you were doing when it popped up, we really cannot tell what the problem may be.

If the bug report pops up, have them get you to that computer to get it to us.

[undnyc]

No there is no message at all. I think for some reason the software will not refresh (database) properly since our timeclock server is in different location. I also notices when time clock is minimized for long time, after restoring it it will display only one name in the program. Some employees complain that they have to search for their timecard in order to punch out.

[undnyc]

Im not getting any messages. For some reason when TimeClockWindow minimized, program wont refresh the list of employees who are in or out. Our database is sitting on the server which is in completely different office. The only way to work around this problem is to completely shutdown TimeClockWindow and then startup. Im not getting a bug report either.

[Paul Mayer]

When you say the database is in a different office, I'm lost on what you mean. Is every computer in the same building and are they all networked together with cable or is it a wireless network? Wireless networks do not work as well as wired. Like in our building, our computers are in four different rooms but are all on a wired network and do not experience what you are. There is a company in the Bahamas that installed TCW on I seem to recall like 30 computers and never had any problems. I'm at a loss on what is happening there.

[undnyc]

I'm sorry for the double post. I have 6 locations that are all in different towns of the state. When I say database I'm talking about having a separate computer dedicated just for hosting TimeClockWindow (data.tcw). Everyone connects to this computer from their stations to punch in and punch out. I'm sorry if I'm confusing you. So everything works over WAN as well as LAN (in one location).

[Paul Mayer]

A How many computers have TCW on them pointing to the database on the server?

Which computers are having the problems, those on the wireless connection or the wired connection?

Are the computers with the problems XP, Win7, Win8 or something else?

If you have problems on XP computers, can you shut them down and then restart and see how it works? We are seeing XP's up like 6 days or more run out of resources slowing things to a crawl.

[undnyc]

I have about 25 computer running TCW all running win7. All the computers are hardwired. We have no XP machines.