Recent content by csr

However, Mike's response has given me an idea ... I may be able to use that same concept to ADD an additional record as the first record of the file. Then the command with the CSV keyword will automatically skip that dummy record. My purpose in all of this is to avoid having to depend upon...

I think these latest thoughts have my original problem turned around. I am trying to solve this problem ... The APPEND FROM ... CSV command automatically omits the first record in the append process. I am looking for some means of getting around this. In other words, I do not wish to omit...

Well, in the absence of any further ideas ... I will put things back to APPEND FROM ... CSV. Other than the fact that it ignores the first record, that works fine. I will check back periodically to see if anyone had a brainstorm. Thanks for your efforts to help. Don

I have discovered the culprit ! It has nothing to do with the 250 characters. That works fine. The problem lies within the memo field data. When the memo field data contains a pair of double quotes ("") the data following those double quotes is deposited in the next available field during...

Well, now I used ... APPEND FROM ... DELIMITED WITH , WITH CHARACTER " and it still causes the MEMO field data to overflow into subsequent fields when the size of the memo field exceeds 250 characters. I am guessing that there is some sort of issue with commas and double quotes being found...

Mike: Also ... I just used DELIMITED in my command and did not include WITH , .... as you have indicated. I thought the comma was the default. I will try it with the WITH clause to see what happens. Don

Mike: I was using APPEND FROM ... DELIMITED but I had a problem with that. It seems that the MEMO field which I was putting into a 250 character field would spill over into additional fields if it contained more than 250 characters. So, I tried putting in the keyword CSV and that corrected the...

When I use the command APPEND FROM ... CSV there is an assumption that the first record contains field names. I would prefer to do this without involving field names at all. There doesn't appear to be any option for this. Is that true ? Don

Don here again ... I mis-spoke on my previous post. I should have said ... It does not respect the STRING DELIMITERS. It processes commas imbedded within a STRING as field delimiters. Don

Tamar: Thanks for the confirmation of bad news. [dazed] TheRambler: I read the article. Tried the software. It is flawed. It does not respect the field delimiters (commas)and processes commas within quotes as field delimiters. I will take a look at it to see if I can discern why it does...

I am appending data from a comma delimited file and everything works fine except for the fact that one of the fields contains more than 254 characters (the limit for a text field). So, I tried changing the field in the target file to a memo field. Now, nothing comes in to that field. Is that...

I need to put the data which is presently in a comma delimited (CVS) file into a Foxpro table. What is the most efficient way of accomplishing this. Without further direction I am left to creating the Foxpro file using the CREATE command and then using APPEND FROM to pull the data into the...

Ok, then ... I will stay with the Microsoft C version 7.1 runtime library. Thanks for your help. Don

Tamar: Thank you for pointing out the NOT / NOW oversight. I mean't to say .. I am NOW attempting to rebuild it in VFP 9. I have since corrected the syntax of the statement and it builds fine now. Thanks for the help from all. Don Don

Mike: I just noticed that the Library I selected was the Microsoft C runtime version 7.1 There is no Microsoft C++ runtime version 7.1 Should I have used the Microsoft C++ version 7.0 instead ? Don