How are you importing the file? Are you automating this import? Are you
using the TransferText command?
You said that you are importing the bad lines, what for? Your data doesn't
look like fixed width, but if you are just trying to import into a single
field then I understand what you're doing there.
What version are you going to use? I prefer A2k but the help files stink on
it.
Scott
<rd*****@yahoo.com> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com...
The file is created by a process that I do not have access to modify.
However, when I parse the file and import only the problematic lines,
they work correctly, each filing into its own row. Is access getting
sloppy in its handling?
If I can't fix this, does anyone have a script to read rows with
multiple lines of data and separate them into their own rows?
Scott Simonson wrote: The first question is what creates this file? It looks like you may
have control characters that indicate end-of-lines or not. You may have to
either strip out these control characters or read character by character
looking for the right CrLf combination to put into a table.
Scott