Internally within Microsoft Access is called a "Legacy database". MS
wants you to use SQL Server with VB Studio or .NET as the front end
for any serious work. Access move from the Jet engine was to allow for
easy upsizing. I've never understood why learn VB for Access and not
just move to SQL Server and VB and leave Access out.
As for comparing them, these are two VERY different products.
FileMaker is at its roots an end-user database that scales up well in
some instances and not so well in others. Access has its roots as a
developer focused db that was was brought into the Office suite and
does a VERY poor job scaling down to the end-user while also choking
as the solution scales upwards, hence MS recommendation to limit it's
use in multi-user scenarios.
People that have worked with Access for years love it. I've attended a
few of the Access Developers Conferences that are put on by the same
people that do the FileMaker conferences BTW! The passion is much the
same but they feel neglected, at least in private, by Microsoft which
has placed its bets with SQL Server and VB or .NET.
- Access vs. FileMaker Jeff
-
