A lot of people think that businesses run on a bunch of complex and expensive applications. SAP, JD Edwards, MS CRM and the like.
The truth is that the vast majority of businesses are SMALL businesses. And a small business usually runs on a combination of an accounting package, pen and paper, MS Word, MS Excel and maybe MS Access.
However, a time comes when a growing business finds that the systems they have been using are now causing them more trouble than they solve. A smart or lucky business finds that out before the whole thing breaks down.
Then they need to progress to a better system.
- Pen and paper moves to Excel or Access.
- Excel moves to Access.
- Access moves to SQL Server, and a web or desktop front end,
- or maybe an off the shelf application.
Applications move from being single user to being able to function with 5 or 10 people using them at once.
A very large proportion of what I do as a bespoke developer involves taking an existing Excel or Access based system, and moving it to the next step.
I'm considering taking an Access application I wrote over 10 years ago, and turning it into a .NET Windows application.
As part of the exercise, I can record the process on video and create a training course out of it.
If anyone would be interested in learning how to convert Access applications to .NET "nicely", drop a comment in and I'll start the process.