If what you need is project management software, be aware that tens, perhaps
hundreds of thousands, of hours go into the typical project management
software product, and Microsoft Project is no exception. Writing that type
of software, too, is a specialty at which not everyone is skilled, and if
you aren't skilled, then it will take much longer. I'd recommend you
consider using Project, or some other project management software, even if
you do not need all its capabilities. Access, as delivered, does not have
any inherent Project Management capability.
And, from my previous "incarnation" as a mainframe specialist in _using_ and
supporting, but not writing, project management software, I can tell you
that you are likely to decide later that you can take advantage of more and
more of the features of that PM software.
Finally, it's worth noting that Project and many other current PM software
products are true bargains. Each release of the mainframe product that I
used and supported would cost the user tens of thousands of dollars, or a
corresponding monthly fee, and it was one of the lower-cost of what was then
"high-end" project management packages. Lots and lots of people licensed it,
and lots and lots licensed its pricier competitors. Some could run as much
as $250,000 installed and running, plus an annual maintenance fee! I'm out
of the PM software business, but because of that background, do try at least
to stay in touch and even the least expensive version of Microsoft Project
seems to have as much or more capability as that mainframe product did.
While I'm always reluctant to advise someone _against_ using my favorite
database product, to me this would clearly be a case of _buy not build_.
Larry Linson
Microsoft Access MVP
