Symptoms
Certain users experience delays when using PCPunch. The delays occur at multiple computers. Other users are not affected.
Cause
If the user pops down PCPunch's Project menu and specifies Non-Project, the punch does not show on the timecard. The punch is recorded in the database along with an outdated setting, which prevents that punch from ever getting processed. This causes WaspTime to verify all existing punches in the database every time this user submits a new punch, which causes delays at punch time.
Workaround
For the PCPunch utility to work correctly, the user should not change the Project menu.
Resolution
To fix an existing slowdown problem, the script below makes a database backup (in case of problems), then updates the bad punches so they will not cause a delay, but also not unexpectedly show up on a timecard.