import txt file not creating new lines

[rdpacer]

I'm importing a text file and would prefer that it create a new row in
the access table for each row in the text file. However, it is
sporadically combing some of the lines into a single row.

eg.
row 1: &a4758v5976HDNOC

row 2: &a4758v7128H 14

row 3: &a4880v432H492733

row 4: &a4880v936H0035-D
&a4880v15125
&a4880v3312HINWC5066

row 5: &a4880v3888H501
I'm not using specs or anything, just a standard fixed-width import -
Access 97. Anyone have a solution for this? Thanks.

[Scott Simonson]

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

<rd*****@yahoo.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
I'm importing a text file and would prefer that it create a new row in
the access table for each row in the text file. However, it is
sporadically combing some of the lines into a single row.

eg.
row 1: &a4758v5976HDNOC

row 2: &a4758v7128H 14

row 3: &a4880v432H492733

row 4: &a4880v936H0035-D
&a4880v15125
&a4880v3312HINWC5066

row 5: &a4880v3888H501
I'm not using specs or anything, just a standard fixed-width import -
Access 97. Anyone have a solution for this? Thanks.

[rdpacer]

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

[rdpacer]

Tried it in Access XP - no problems. I suppose this is a 97 bug.

[rdpacer]

Tried it in Access XP - no problems. I suppose this is a 97 bug.

[Scott Simonson]

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