A decade ago the large company I worked for switched to a web based timecard system. The only problem, ie only and the software team of 50+ all were using hpux or solaris workstations. No ie. Oh and they wanted timecards done daily.
The solution?
Set up 2 terminals in the lab with a unix backend and a windows NT virtual environment so we can use IE to do timecards.
How complicated can/should a timecard system be? Surely one of those 50+ software engineers could have rewritten a portable version in a few days and saved you a lot of bother.
Comments
I thought things had gotten better.
A decade ago the large company I worked for switched to a web based timecard system. The only problem, ie only and the software team of 50+ all were using hpux or solaris workstations. No ie. Oh and they wanted timecards done daily.
The solution?
Set up 2 terminals in the lab with a unix backend and a windows NT virtual environment so we can use IE to do timecards.
How complicated can/should a timecard system be? Surely one of those 50+ software engineers could have rewritten a portable version in a few days and saved you a lot of bother.