Importing Text

[martin]

I have a field in a text file that has imbedded double-
quotes ("). Access will not import these fields and the
import causes an Unparsable Record error for each record
that has such a field. I have tried several different
separator characters like comma and pipe in the original
text file, but nothing seems to make a difference.

Is there a way around this? Any ideas would be helpful.
Thanks.

 

[John Nurick]

Hi Martin,

This normally works just fine. Here are the contents of a pipe-delimited
text file I've just imported:

Field1|Field2|Field3
1|Text field|Text Field
2|Field with "quote" marks|Text Field
3|"Field within "quote" marks"|Last Field

As you go through the wizard, make sure you select
Delimited file
For delimiter, choose "Other" and type a | in the box
(make quite certain the box is empty first)
First Row contains field name
Text qualifier: none

If this doesn't help, please post back with a sample of your data and
details of theversions of Access and Windows you are using.

 

[martin]

John
I believe I missed the Text Qualifier None setting when I
was doing this

Thanks for the help.

-----Original Message-----
Hi Martin,

This normally works just fine. Here are the contents of a pipe-delimited
text file I've just imported:

Field1|Field2|Field3
1|Text field|Text Field
2|Field with "quote" marks|Text Field
3|"Field within "quote" marks"|Last Field

As you go through the wizard, make sure you select
Delimited file
For delimiter, choose "Other" and type a | in the box
(make quite certain the box is empty first)
First Row contains field name
Text qualifier: none

If this doesn't help, please post back with a sample of your data and
details of theversions of Access and Windows you are using.

I have a field in a text file that has imbedded double-
quotes ("). Access will not import these fields and the
import causes an Unparsable Record error for each record
that has such a field. I have tried several different
separator characters like comma and pipe in the original
text file, but nothing seems to make a difference.

Is there a way around this? Any ideas would be helpful.
Thanks.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.