rotny
asked on
Error during import of pipe-delimited text file
I tried importing a pipe-delimited text file and got the following error: Could not find the selected row delimiter within the first 8kb of data. Is the Selected row delimiter valid?
FileType: ANSI
RowDelimiter: {CR}{LF}
Text Qualifier: None
FileType: ANSI
RowDelimiter: {CR}{LF}
Text Qualifier: None
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I believe the solution given should have solved the problem. It was straight out of the documentation. But no response.....
It is a pipe-delimited text file that the author mentions. In this case, instead of using '\r' or '\n', the delimiter should be changed to '|' as I mentioned earlier.
I hope the author gets back on what is the field-delimiter and row-delimiter for the text file.
I hope the author gets back on what is the field-delimiter and row-delimiter for the text file.
True, it is a pipe delimited. But the problem wasn't in delimiting fields, it was in finding the end of line...the row delimiter was bad.
Yes, and that is where I would like to ask the author if the row-delimiter is indeed a CR or LF?
The text file could have single field pipe-delimited values, in which case it becomes the row-delimiter.
And I made the above comments based on the assumption that '|' is the row-delimiter (since the CR/LF are not found).
The text file could have single field pipe-delimited values, in which case it becomes the row-delimiter.
And I made the above comments based on the assumption that '|' is the row-delimiter (since the CR/LF are not found).
Ah, I see. I guess I've never had that happen. The only time I've seen this error is when files are moved between machines and the CRLF at the end of the row comes through as only CR or LF.
In this case, are you sure the CRLF transforms to CR or LF when the files are transferred across machines? Storing the CRLF as CR, LF or CRLF is based on the Operating System (AFAIK) and this should happen only when you save a text file locally. In my experience, transferring files retains the CRLF, say from Windows to Linux. Hmm, shifting away from the topic, eh?
I guess we better wait for the author to throw more light on what row-delimiter the text file actually has.
I guess we better wait for the author to throw more light on what row-delimiter the text file actually has.
in the screen 'Select file format', you need to select 'Delimited': the default is 'Fixed fied'
and in the next screen 'Specify Column Delimeter', you can specify the pipe symbol | in the textbox.
hope that helps.