Best Approach for a Quick & Dirty Desktop Application
Nov 03, 2008, 13:03 (0 Talkback[s])
(Other stories by Phil Hughes)
WEBINAR: On-demand webcast
How to Boost Database Development Productivity on Linux, Docker, and Kubernetes with Microsoft SQL Server 2017 REGISTER >
"The application is for some not very fancy record keeping. You
could call it a payroll system but it has few of the
characteristics of a real payroll system. Also, it is
temporary—in a few months it will be no longer needed. It is
for the Geek Ranch project and is to keep track of "casual
"We have anywhere up to 50 people working on various
construction projects. They are paid (in cash) every two weeks.
Their pay is based on days worked during the period at a daily
rate. The "twists and turns" are minimal (getting paid for seven
days if they work six, for example) but that can pretty much be
dealt with by hand.
"There are reasons this becomes a database project rather than
just a spreadsheet:"