Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
APPEND FROM inconsistencies
Message
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
01085187
Message ID:
01085478
Views:
19
>>>>Peter,
>>>>
>>>>I doubt that you may get consistent result with inconsistent information here. The delimited format has limitations, and you ran in one of it when using delimiters that were already used as information piece.
>>>
>>>How do you mean, inconsistent information?
>>
>>I mean, there are Special/Reserved characters that are used for special purposes, and here they are (quotation marks, ", ') used in particular for delimiting.
>>If the record contains those characters, then it is no common way to recognize some of them as information, others as delimiters.
>
>This is odd reasoning. Of all characters that are used to delimit character values, the double quotation mark is the most common! DELIMITED WITH is especially used to specify the character value delimiter. So, specifying " is a very logical action.

Cannot see any logic to use quotes HERE as delimiters, because they already used as a valid information in the record. There us no way to distinquish between those quotes belong to record, and used as delimiters.

>
>>>
>>>>You need to use the delimiter other than double or singles quotes here.
>>>
>>>Most notably the 1st statement is often advised here.
>>>
>>>>By the way, I did not have any problem with your fourth statement; and it was the only one that gave the consistent result.
>>>
>>>What a coincidence! For the sake of clear code I added a space behind the quote. Please redo the statement, but now without the additional space:
>>>
append from tabdeli.txt type delimited with '  with character TAB
>>>append from tabdeli.txt type delimited with ' with character TAB
>>
>>Anyway it would be better to avoid using reserved characters/words for not their direct purposes. Otherwise you may get unexpected results.
>
>Did or did you not get the error?

Error on the second line.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform