Comments on: Handling Delimeters in CSV Files

By: Jon Peltier

Jon Peltier — Mon, 18 May 2009 13:16:00 +0000

David -

I think you need to find some VBA tutorials. You could buy VBA for Dummies, or you could Google for VBA tutorial.

By: Doug Jenkins

Doug Jenkins — Mon, 18 May 2009 04:19:00 +0000

David – if you have copied and pasted the code without change the most likely problem is you don’t have write access to C:. If you change C: in the code to the full path to your Documents folder (or any other folder you know you have write access to), it should work.

By: David

David — Mon, 18 May 2009 00:53:00 +0000

Thanks for the reply Jon.

As I am just trying to get my head around VBA can you please explain how to 'define sFname and lFnum'

By: Jon Peltier

Jon Peltier — Thu, 14 May 2009 13:28:00 +0000

Have you defined sFname? and lFnum?

By: David

David — Wed, 13 May 2009 01:36:00 +0000

I have been trying to use MakeCSV2 and the following error occurs when I run it

Run-time error '75':
Path/File access error

When I click on the Debug button the following line is highlited

Open sFname For Output As lFnum

Any help would be appreciated

By: Larisa

Larisa — Thu, 08 Jan 2009 17:09:00 +0000

In you code comma Chr(44) can be replaced by CHR(130).
Chr (130) looks just like normal comma, but doesn't split the field in CSV

By: srinivas

srinivas — Wed, 12 Nov 2008 12:58:00 +0000

sir

i have excel file which was converted to .csv file in that one row have 14 characters number field but once i save and open it is giving 1.33333+4 error. Actually i want to upload a .csv file to our software because of this error i cannot do

By: Bert

Bert — Tue, 28 Oct 2008 09:44:00 +0000

I stick to tab delimited files whenever possible - they just work better.

Leonid,

The example you gave shows the downfall of the SaveAs CSV method - Excel's inconsistent use of quote marks. There are many programs that cannot read this style of CSV properly, including (ridiculously) Microsoft Access. That's why we often need to roll our own CSVs.

By: Tobias Schmid

Tobias Schmid — Fri, 24 Oct 2008 13:36:00 +0000

Damn! Error! I confused the numbers! Here's the correct version:

Here are the three approaches:
1. Using "SaveAs csv"
2. Reading the data in a range -> use print
3. Reading the data in a variant -> use print

And that's the result:
1. 5.2 seconds
2. 4.7 seconds
3. 1.2 seconds

By: Tobias Schmid

Tobias Schmid — Fri, 24 Oct 2008 13:35:00 +0000

@Rob Bruce
I've compared the elapsed time when exporting data using the "SaveAs csv" and the "print"-function. I don't think there is a big difference in time necessary. More important is how you get the data out of the excel sheet.

Here are the three approaches:
1. Using "SaveAs csv"
2. Reading the data in a variant -> use print
3. Reading the data in a range -> use print

And that's the result:
1. 5.2 seconds
2. 4.7 seconds
3. 1.2 seconds
(for the setup see here: http://www.vba-blog.de/?q=content/datenexport-textdatei-mit-print - Sorry! It's only a german website, but I'm still working on my english. )

If there are a lot of formulas in the workbook, the "SaveAs csv" will take even more time. So I would never recommend using the "SaveAs csv"-macro.

I will try to implement your "huge empty string" and compare it with the others.

Nice weekend!
Tobi