From a purely data management point of view, I have thoroughly enjoyed
developing databases using Filemaker Pro and MS Access.

I am more familiar with older version of Filemaker Pro, but I assume the
more recent versions (with which I have less experience) as essentially the
same. Filemaker has some pre-established scripts which are easy to put
together to do relatively complicated tasks, and basic but useful things
like stripping (removing spaces from each end of field) or concenating (I
spelled that wrong) - the addition of one field to another to create new
data, like First Name plus Last Name = Name. Filemaker allows more novice
users to do all that interesting stuff without Visual Basic, which you have
to do for some of the more complicated things in MS Access. I produced a
series of databases in Filemaker Pro to help a previous employer control
information better, including assigning unique identifying serial numbers to
most artifacts, even for small projects, all taken care of by the database.
Filemaker Pro no longer has mobile support (save for the iPhone, which I
probably wouldn't suggest taking into the field).

MS Access is more complicated, but that comes with benefits. As long as you
are using an .mdb file (I think in MS Access 2007 you can also use a new
type of database file, but .mdb files are still the default) you can
integrate tabular data with GIS data. MS Access runs on the same Jet
database engine as ESRI's personal geodatabase GIS file. The two files are
interchangable. For small businesses and land managers for small parcels,
saw a coupe thousand acres, this is a powerful way to integrate GIS and
tabular data management in a single application in a very cool way. I have
enjoyed learning how to user MS Access and have developed several database
applications for my local Heritage program. I have also been able to
integrate separate databases to increase the power of each database. There
is no longer mobile support for MS Access. However, if you google MS Access
mobile you will be able to find some purchasable Visual Basic mobile apps
that allow you to run MS Access databases on mobile devices, which can help
in the field (I am a fan of direct data entry in the field, and then
manipulating that data using forms to produce certain parts of a report...a
big time saver). If you are so inclined, and have some extra cash, there are
also Microsoft mobile developer tools, for a price, to develop your own
mobile applications. Of course you can also simply take a computer into the
field.

A key use of relational databases can be twofold, to force people to enter
specific values into a field and reduce the bloating of the number of fields
normally encountered in spreadsheets. Not only can you limit the values
allowed in a field using forms or post-data entry checking, but you can also
limit the number of fields (if the archaeological spreadsheets I have often
seen are any indication) by better defining the way in which you handle the
storage of information.

Both MS Access and Filemaker Pro support user permissions controls for
multiple levels of access, as I understand it, though I have never employed
this on my databases (they already sit behind password-protected servers).
This can be useful if you want to maintain the physical security of data
(avoid accidental deletion).

For agency folks who can afford it, at the Forest Service we have an
excellent, integrated, Oracle database. It allows us to manage an incredible
amount of data, with a lot of controls on access and editing priveleges. But
I suspect this is beyond the means of many people, and is more powerful than
most people need.

-Max Dean