ouch, the custom delimiters finally soaked in; that' certainly adds tot eh complexity, since i'd normally BULK INSERT something custom delimtied...but you need the tables built on the fly, based on the table name,

The Import/Export wizard does custom delimters real well, but it's really single-file-scoped, i think, and doesn't do all files nicely.

i've got a TSQL solution from long ago, where i changed the registry settings for the driver to a tab instead of the comma, but that was using the JET driver, and not the ace;

once you change the setting in the registry, it's important to change it back;

i'll test my solution now, but i'll have to find and replace the current commas with ¶, and test it from there.