Lynn:

A bit more - 

The site you've referenced uses the reporting function of Access to
produce EAD. To my primitive, non-programmer understanding anyway, this
was, for a long time, really the only way to directly get XML from
Access. However it isn't perfectly straightforward. There could be
problems with getting data out of word - be careful which save format
you choose or you might get characters that won't parse. Also, the
report will add a whole bunch of extra spaces and returns which will
probably have to be stripped somehow. There are other potential
difficulties.

Using later versions of Access allows you to do XML reporting more
easily,  and will (to some degree) work on hierarchical data. Anyhow, as
I see it, it's a more straightforward task to use XSLT to transform
clean data from the automated XML output of Access 2003 and later. If
you have to clean up the data after creating the report, there's an
extra step where error can creep in. 

As an idea, you might look into doing the same thing the SunSite
suggests with older forms of the database with the newer, perhaps making
transforming the data a matter of stripping out the prefixes Microsoft's
Access's XML function places in XML tags rather than transforming the
whole document.

Chatham


-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf
Of Lynn Lobash
Sent: Tuesday, March 15, 2005 3:41 PM
To: [log in to unmask]
Subject: Re: Access to EAD

I found this at Berkeley's Sunsite and it looks like a good solution for
this project.

http://sunsite3.berkeley.edu/FindingAids/uc-ead/tools/database/

Thanks for the help.

Lynn