David:

I've now reprocessed the Michigan data
	
	a) to include DDBDP links (cu510_dd fields)
	b) to include normalized Date1/Date2 fields

(I've also corrected the cu245ab problem you noted previously.)

I've uploaded two versions of the file again (which are you using?):

http://www.columbia.edu/cu/libraries/inside/projects/apis/michigan/output/umich_desc.TAB
http://www.columbia.edu/cu/libraries/inside/projects/apis/michigan/output/umich_desc.BAS

Also, there are links to detailed specs below which may or may not help 
answer questions:

http://www.columbia.edu/cu/libraries/inside/projects/apis/michigan/specs/510_dd.html
http://www.columbia.edu/cu/libraries/inside/projects/apis/michigan/specs/dates.html
http://www.columbia.edu/cu/libraries/inside/projects/apis/michigan/specs/special.html

Let me know if you have problems.  I've noted, by the way, that some of the 
data fields have embedded control characters; also, there are occasional 
bits of HTML floating around in the data, who knows why.

As you can probably see, because Filemaker Pro has no programming language, 
I've had to take multiple, hopefully mutually exclusive shots at converting 
some of the fields.  This leads to a lot of empty fields in the output 
files, but you can just delete them, since only the fields with content 
matter, and those include their own MMF content designation.

There's a possibility, however, that some non-repeatable fields got 
repeated by error.  If that happens, I can fix easily, but I can't really 
see them in advance with the functionality available in FMP.

/Stephen