James,
 
It sounds like your database isn't going to be too large with just
several hundred artifacts.  Peter Northover is correct in stating that any
relational database program should serve your needs.  Any software
designed specifically for archaeological applications will probably cost
quite a bit more.
 
In terms of coding for type of item, the materials you have and how
you've analyzed them will dictate that, but it's important to develop a
standardized list of terms to be used. And don't deviate from it. I've
done a lot of work with archaeological databases and strongly recommend
using at *least* two fields to describe an item. For example, one would
be a general material description, while the second describes the
artifact, e.g. field1: ground stone  field2: mano.  Then you can generate
statistics or reports on whichever level of detail you need.  But it's
*very* important to keep the fields conceptually distinct.
 
And remember that the design of a database is more important than the
actual software package used, especially if you're using off-the-shelf
software.  Take advantage of the relational capabilities to decrease data
redundancy, develop standardization and enforce it, and document your system.
 
I've done a few papers/posters on database design in the past few
years that get into more detail. Let me know if you'd like to see them.
 
Good luck.
 
Mary S. Carroll
Information Management Specialist
National Center for Preservation Technology and Training
NSU Box 5682
Natchitoches, LA 71497
318-357-6464
318-357-6421 fax
[log in to unmask]
gopher://gopher.ncptt.nps.gov