Data Import from a CSV file

Posted on 2014-08-07
Last Modified: 2014-08-07
I have been supplied with a text file with comma separated values which require update to a database.

When read in programmatically the string has an ASCII Null between every character
eg.   D A V 0 0 1 , J u l i e , D a v i e s - J o n e s ,

In notepad the file displays correctly as DAV001,Julie,Davies-Jones

The supplier of the file is downloading the file from a web site of an international company so I am unable to contact the originator.

Since Notepad is automatically stripping out the nulls is there a Windows API function I can utilise to replicate the Notepad functionality
Question by:TomPreen
    LVL 29

    Accepted Solution

    Notepad is not striping out the NULLs, but notepad is capable to identify Unicode, while fox is not.

    The simple solution: Stripe off chr(0):
    ansi = chrtran(unicodetext,chr(0),'')

    Open in new window

    The correcter solution
    ansi = ?Strconv(unicode,6,1252,1)

    Open in new window

    You'll have an additional problem, as most probably notepad added a few bytes called BOM (byte order mark) marking the rest of the file as Unicode, so record 1 pr the first field name might contain unwanted characters.

    Another simple solution is to save again with notepad via Save As, then set the encoding to ANSI instead of Unicode.

    Bye, Olaf.
    LVL 23

    Expert Comment

    What i normally do if i have converting issues is trying to open the CSV in Excel because it holds it's original information and then copy and paste it into NotePad. Normally this does do the trick. The only other option is to ask for a correctly configured file..

    Author Closing Comment


     I have done hundred of imports using Fox Pro over the last 10 years and I have never seen this issue before.
    LVL 29

    Expert Comment

    by:Olaf Doschke

    more typical for internet services is UTF-8 encoding, which encodes the most commonly used 128 characters (eg letters, digits) in the same way as ASCII and many ANSI codepages. That's why you might never have stumbled upon this, even if you already precessed UTF-8 data only using these 128 characters.

    Unicode (specifcally ISO 10646) is capable to encode more characters, it defines 17 planes with each potentially 65535 characters. Unicode Version 7 is "just" using 113.021 of theses potential codes.

    MS mostly uses UTF-16 for Unicode, which is using 16bits or two bytes for most characters, no characters are encoded with a single byte, also the simple ones of ASCII or of ANSI codepages, so you surely stumble upon this encoding problem the first time you get UTF-16 data.

    Character/Text/Data encoding (in the sense of codepages, not in the sense of cryptographic encoding) is a topic you should be aware of at least, even if you stumble upon this for the first time. Unicode is one of the weaknesses of VFP you can only partly cope with. You can easily store unicode in binary fields, but the native VFP controls will not display unicode and you have all kind of symptoms with it. Some operations will irreversably change unknown chars with '?' and so you always better keep original files for postprocessing into something VFP can work with, once such conversion losses in data are recognized.

    Bye, Olaf.

    Author Comment

    The file in question had one other thing that I have not seen.

    The first two characters were ASCII 255 and ASCII 254.

    Is this a signal that it is Unicode?

    Also Excel does not recognize the file as a CSV file in the conventional way by creating columns for each comma separated variable, all values for each line appeared in column A separated by commas
    LVL 29

    Expert Comment

    by:Olaf Doschke
    >The first two characters were ASCII 255 and ASCII 254.
    This is the BOM I mentioned earlier. Look that up in Wikipedia and you get it explained.

    >Is this a signal that it is Unicode?
    Yes and no. It's just a few applications setting and expecting a BOM at the begin of a file. In other cases files may simply be Unicode without any hint in itself. Today XML is more common and has standard tags and attributes defining the encoding.

    You may use the first two bytes as indicator, but not as proof.

    Bye, Olaf.
    LVL 44

    Expert Comment

    That might be the BOM (byte order marker)

    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Join & Write a Comment

    The new Microsoft OS looks great, is easier than ever to upgrade to, it is even free.  So what's the catch?  If you don't change the privacy settings, Microsoft will, in accordance with the (EULA) you clicked okay to without reading, collect all the…
    This collection of functions covers all the normal rounding methods of just about any numeric value.
    The viewer will learn how to use the =DISCRINV command to create a discrete random variable, use this command to model a set of probabilities and outcomes in a Monte Carlo simulation, and learn how to find the standard deviation of a set of probabil…
    This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA.…

    746 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now