After spending about an hour to post this
----------------------------------------------------------
If you have your data (perhaps after filling some cells with VBScript
code) in an Excel table (sheet), it's fairly easy to export this to a
pipe-delimited text file by using
(a) Excel automation
Use the macro recorder to get the code to export the sheet
into a text file paying special attention to the specification
of the delimiter
Port/Translate the recorded macro code in a simple Excel
automation script (cf.
http://www.visualbasicscript.com/fb.ashx?m=84683 )
(b) ADO
Specify the format for the text file in a schema.ini file (you
could use some of the information from your .xsd)
Connect to your Excel .xsl via ADO
Do a SELECT resp. INSERT INTO ExternalDB statement
Writing your own interpreter for .xsd files is way more complicated.
----------------------------------------------------------
I'm fairly sure that simple text with just a few punctuation marks or
special characters (slash, dot dot dot, to name a few) is too much
for the parser that handles the input. Evidence: the preview doesn't
succeed in that case neither.
This
Do a SELECT resp. INSERT INTO ExternalDB statement
Started as
Do a SELECT slash INSERT dot dot dot INTO ExternalDB statement
I couldn't preview or save this text as long as the last line had
the 'masked' characters.