For the benefit of others, here's what I found in response to the file sent:
* Specify Text File as data source
* Choose "Delimited" file format, ANSI, {LF}
* Check first row has column names
* Click [Next]
* Specify Other column delimiter and type a single space in the edit box
* Data is now correctly parsable by your columns.
[quoted text, click to view] "Scot T Brennecke" <ScotB@MVPs.spamhater.org> wrote in message
news:eJeoeP4kFHA.2444@tk2msftngp13.phx.gbl...
> You can send the file to me at the following address (remove spaces and use punctuation as
> indicated):
> S c o t B at M V P s dot o r g
>
> "kayda" <tabladude@gmail.com> wrote in message
> news:1122561389.451268.18530@f14g2000cwb.googlegroups.com...
>> Hi:
>>
>> I have setup DSNs before to text files with some success. I am having
>> problems with a file I have to parse to pump into SQL Server via DTS.
>> It appears to be fixed length (what does the 'length' refer to
>> normally-the text plus the spaces to get to the first character in the
>> next column?). I keep getting errors saying there is a problem with the
>> schema .ini file, or it just recognizes the file as one field. I've
>> tried using tab delimited as well but no luck.
>>
>> It's perhaps hard to describe this-I could send the text file along if
>> someone would like to have a look. If there are any other ways other
>> than ODBC of parsing a difficult text file please let me know.
>>
>> Thanks,
>> Kayda
>>
>
>