Great, thanks.
I'm looking forward to your solution!
OK... here's a workaround, although it's not automated. Maybe when scott_r finishes his rewrite of MC XML Export it will support XSLT2.0, which I think allows the create of two outputs. It will soon become clear why this is needed.
If you run the export without the lyrics field, everything should be just fine. Then:
1. Go ahead and import this into Access as described in the preset documentation.
2. Then manually add the lyrics field - it's probably important that you put it where it belongs (i.e. after Last Played and before Media Type). Make sure the field data type is memo vice text.
3. Export the MediaItems table (File->Export->(Save as type xml and Filename "MediaItems" in the same directory you exported the XML to)->Export->(check only Schema...)->OK. This will create MediaItems.xsd in the same directory as the exported XML.
4. Export the XML with MC XML Export, but this time check the Lyrics field.
5. Replace the second line of the exported XML to
<dataroot xmlns:foo="NoURL" xmlns:od="urn:schemas-microsoft-com:officedata" xsi:noNamespaceSchemaLocation="MediaItems.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
This associates the XML with the schema.
6. Import the XML into access - you can either start a new database or delete the old table.
That's it. You'll only have to do most of this once. The only thing you'd need to repeat is step 5 every time you export the XML from MC. If you find this works well for you, I can automate this for you.
So... if XSLT2.0 lets you create two output documents (I'm pretty sure it does), I could automate the creation of the XSD at the same time the XML is created. But until scott_r adds XSLT2.0 support (or rather, if...) there's nothing I can think of to automate this.
Sorry the explanation is worded a bit poorly - I don't have the time right now to make it more succint. If you need specific help, let me know...