Hi Tess and everyone else. I found Tess’s post most helpful because she included a lot of the “big words” that are involved in those skills. It makes it very easy to see whether you have that skill or not. If you understand what she’s saying, then you might be ok. If it seems she’s talking Greek, think twice about offering it – or make it clear about what you can offer.
I’d like to add Access database development to the pot. It can seem easy to build simple tables, queries, forms and reports – and that may sometimes be all you need. But it can get complicated real fast. I think the difference lies in what the client is looking for.
If they just ask you to compile a report from some data they have, then you can use whatever tools you want to build that report (including Access).
But if they see “database development” on a list of services, they may ask for a database to be built for their own use. And that is a ton of work. There’s the design work, consultations, security, data design and integrity, relational tables (as opposed to simple tables), table relationships, normalization, SQL, VBA programming in modules/macros/objects/forms, multiple-user issues, training, setup, implementation, maintenance, version issues, etc, etc, etc – many things to think and worry about. Not to mention all the different computer and server configurations out there – you’d need to make sure it works on their computer(s) and that they have the proper versions of the software as well (and if they later upgrade to a higher version, your database may stop working properly). If they don’t want to buy Access, then you would need to develop it “stand-alone” and that means different expensive software you would need (and that could involve operating system upgrades on their part). Plus all the changes and updates the client will inevitably have – they often do not really know exactly what they need or want in the beginning (or can’t explain it, or think it’s obvious), but start to see it once you have given them a taste. You need to try to think ahead to what they might be forgetting to ask for, given what you know about their specs. There is so much extra work to do when you build a database for someone else to use. You need to charge a LOT more.
It’s like building websites (and many other things) – there’s the easier wizard/template way that will get you to a certain point. And if that's all that's needed, that's ok. But if you need more, you'll need extra training or to call in a professional. And the professional will probably just start over from scratch because it's usually easier than working with someone else's database.
Of course, I can only speak from my experience. I did database development and programming for 10 years and I have no desire to offer it as a VA service. Far too much work. I definitely commend those of you that do do it, as you have probably found a way to make it work. All that said, I love working with Access. It’s my favourite tool to use. I would certainly plan to advertise a service for data collection and reporting – or some such other term.
Sorry for the very long-winded post and run-on sentences and bad grammar.
Deb
p.s. I think this long post should count as 2 don’t you? I need to get my post count up.