Sanity prevailed at work this week when a clunky looking VB timesheet application was finally replaced with a slick web interface. I think we were the last company on the planet not to use a web interface for timesheets.
Between OpenOffice and the new time reporting interface, I have even less reason to use my Windows box.:)
I think we were the last company on the planet not to use a web interface for timesheets.
[Because of this change] I have even less reason to use my Windows box.:)
My work is (trying) to replace its current timesheeting systems with a single web-based timesheeting system. Niggle is that it's based on Oracle forms and is a bit clunky. Big problem (to me) is that although it's web based, it uses sufficient JavaScript that it doesn't work on anything other than recent IE. So not only can't I use it on m
Timesheets (Score:1)
I guess we are only company who use CSV + CVS as a storage format for timesheets and a couple of Perl modules to query them and publish on TWiki :)
Ilya Martynov (http://martynov.org/ [martynov.org])
timing (Score:2)
I think we were the last company on the planet not to use a web interface for timesheets.
We used to be a big user of the timing app you got with quickbooks and now we've got an in-house c# desktop app to act as big brother.
some web interfaces are more equal than others (Score:2)
I think we were the last company on the planet not to use a web interface for timesheets.
[Because of this change] I have even less reason to use my Windows box. :)
My work is (trying) to replace its current timesheeting systems with a single web-based timesheeting system. Niggle is that it's based on Oracle forms and is a bit clunky. Big problem (to me) is that although it's web based, it uses sufficient JavaScript that it doesn't work on anything other than recent IE. So not only can't I use it on m