mokaplanjr
Technical User
I have set up a text file DSN and a query that successfully pulls data from the text file. The file is set up with pipe (|) delimiters. This is a read-only situation; the text file will be uploaded via a web form... already set up. It never gets updated by the web application.
The problem is that a field with text (set in the schema.ini file as data type "LongChar"
sometimes has double quotes as part of the text. It may also have carriage returns. This is the way it comes from the original database and, due the nature of the original database's use, can't be changed.
When looking at the text file directly, the data is all there, but the query cuts a row off when it hits either the double quote (so the phrase 'THE FISH IS 12" LONG' becomes 'THE FISH IS 12' -- then the row ends. The same thing happens with carriage returns.
Anybody out there with experience preventing such "illegal" characters as double-quotes and carriage returns from truncating a text field that comes from a flat text file? Could a different delimiter help (although I chose the pipe because it is the least likely to be keystruck when entered with the original data.
Or would changing the field's data type in the schema.ini make a difference?
The problem is that a field with text (set in the schema.ini file as data type "LongChar"
When looking at the text file directly, the data is all there, but the query cuts a row off when it hits either the double quote (so the phrase 'THE FISH IS 12" LONG' becomes 'THE FISH IS 12' -- then the row ends. The same thing happens with carriage returns.
Anybody out there with experience preventing such "illegal" characters as double-quotes and carriage returns from truncating a text field that comes from a flat text file? Could a different delimiter help (although I chose the pipe because it is the least likely to be keystruck when entered with the original data.
Or would changing the field's data type in the schema.ini make a difference?