We Buy Cars / Used Car Club
Broken SQL replication and a leaking data warehouse fixed first, then six years replacing the Access system the floor ran on with a desktop client over a web-service layer.
All work · Commerce & services
A WPF and Silverlight field labour capture system with an approval chain and pay-period rules, replacing an Access front end, and a web-service layer removed when it proved unreliable over the VPN.
Technicians' hours, meals, travel and mileage against job sites were reaching accounting through a slow Access front end, with no approval chain and no way to catch duplicate dates or pay-period errors.
The field capture system with a signature step, then the approval chain above it: a project-manager module approving in runs, a self-mailing five-day report, pay-period and duplicate-date rules, and a browser-based administration application replacing the Access front end.
When the web-service layer made the program unreliable over the VPN, removed it and had the program talk to the database directly. Ran in production and was handed over with source.
Stack
Tell me what it does, what it is written in, and what breaks when it goes down. I will say plainly whether I can help and how I would approach it.
Tell me what it runs on