Creating Access Databases as a Job

[bondtk]

I love to create Access databases. The ones I've created thus far have been
well received by those who use them in my past jobs. My primary job function
was not to create databases, but when I saw a problem that could be fixed
with a database, I start working. People ask how I know how to create them,
and I tell them just by using the program over the years. (I don't usually
mention all the helpful code and ideas I get from here!) I was just
wondering if there are people out there who develop databases for small to
medium size companies say maybe as a part-time or full time job? If so, how
did you get started. How successful is it?

 

[Dirk Goldgar]

I love to create Access databases. The ones I've created thus far
have been well received by those who use them in my past jobs. My
primary job function was not to create databases, but when I saw a
problem that could be fixed with a database, I start working. People
ask how I know how to create them, and I tell them just by using the
program over the years. (I don't usually mention all the helpful
code and ideas I get from here!) I was just wondering if there are
people out there who develop databases for small to medium size
companies say maybe as a part-time or full time job? If so, how did
you get started. How successful is it?

I think you'll find there are lots of us here. I'm one, though I do
lots of other programming work as well. Still, I'd say that Access
work -- development and consulting -- accounts for 80% or more of my
income. I started years ago when, as a programmer working for a small
information services company, I picked Access as the best platform for
an application to be built for one of our clients. A few years later,
when my employer closed up shop, I decided it was time to become my own
boss, so I started my own company, which has somehow managed to survive
to this day. I'm not raking in the dough, by any means, but I'm doing
okay.