>>>Has anyone encountered a problem of improper
>>>importing of ASCII comma-delimited files into
>>>PROPERLY structured table with APPEND FROM...
>>>...TYPE DELIMITED??? When the source
>>>file contains embedded quotation marks or
>>>apostrophies, the remainder of the string in the source
>>>file gets imported with the shift to the left (I am not sure
>>>if I defined it correctly...) Of course I found the way
>>>around it by writing a conversion program with my
>>>favorite low-level functions :), but I want to know if there is
>>>a more efficient sollution.
>>>
>>>Appreciate if this at least will start some communication :)
>>
>>There is a DELIMITED WITH Delimiter option for APPEND FROM that allows use of a character other than quotation marks. I had some data to import into VFP that had quotation marks, so I used ^ as the delimiter. Question mark also worked well for me.
>>
>>Jim
>
>That does not resolve the problem! If you have a choice of
>formats to create, - of course you would choose the easiest
>to work with! I normally choose ASCII TAB DELIMITED!
>But what if the COMMA DELIMITED is the only one
>available????? I have to deal with data that came from
>a rigidly written exporting routine that does not create
>anything else BUT ASCII COMMA DELIMITED!!!
>(BTW, the question was:
>
>... I want to know if there is a more efficient sollution.
>
>...But thanks for reply anyway :)


(This is my first time on here so if I screw up let me know.)
I have found that even if an import ASCII file is delimited
with qoutes or whatever, it may sometimes still not work the
way you want. I have found in these cases that (sometimes)
you can use DELIMITED WITH BLANK. FoxPro seems to be able to
add this to the other delimeters and come up with what I want.
At least it's worth a try. Let me know how it works out.