>Hi again
>
>I'm sorry to bother you again on timetracker thingie, but I think I've added a handy feature that I don't want to keep for myself: If the project is VFP-based, and if it has a customer assigned, when you add it to the database, the program can insert a hook into pjx. Whenever you open the project, a record is written into backend. When you close it, the exit time is written too.
>
>My problem was it was hard to keep time: how much I've worked and for who. This feature is pretty good in this matter.

Christian's TimeTracker Pro has the feature 'Audit Trail'. It appears to record each action, so likely also the opening and closing of project files.
Clickwork doesn't do that. I personally dislike the idea of a Big Brother who's watching me. In Clickwork it is the USER who decides the start and end times and the kind of recorded activity. These can even be revised later. Having said that, I must admit that the next version will contain a very flexible user access system. It is so flexible that the manager can even turn CW into a small big brother.

CW is a separate app, not working in the IDE of VFP. Letting CW act upon an opening/closing of a PJX requires quite special programming by me. However, I guess someone could add a record to its activities table (defaults to Activities.vcw) with a project hook, and then use CW to print reports and the like.