Another possible approach would be to
construct a 'front-end' to an Access
database: the immediate one that comes
to mind is Visual Basic, which works
quite nicely as a front-end.
Those who are conversant in both agree that it takes at least three times as
much time and effort to create the same program in VB as it does in Access,
and often more, even with "classic VB" (VB6 or earlier). Many of us believe
that it there is even more disparity between development time/effort when
using VB.NET.
And, in this regard, VB is the "best of the lot." I believe you may still
find a presentation I did for my user group on the subject at
http://appdevissues.tripod.com.
There are some conditions in which using VB as a front end is justified, but
generally, you will be time, money, and frustration ahead by using Access
and the runtime.
Larry Linson
Microsoft Access MVP