Bob presented the following explanation :
Why is there no comma after the 600, which is the last cell used in each row
? Shouldn't there be per your reply ?

As my reply states, there is no comma after the 2nd "x" because (as
joeu2004 points out thoroughly well) it's the last piece of data in the
row. As Claus states, if there's any of the characters he mentions in
cells following the cell containing '600' then you will see more
commas.

As Bruce states, the values are *separated* by commas meaning the
commas act as deliminators of the data fields. Delimiters separate the
fields in the file! (Contrary to Bruce's assertion that a CSV is NOT a
comma delimited values file; when in fact it is<g)

So here's an example that sums up what everyone is trying to convey...

x,x,,,x

...where there are 5 data fields of which only the first 2 and last 1
contain data. Say, for example, you have the following data table...

FirstName,LastName,Address1,Address2,State/Prov,Zip,Phone1,Phone2,Fax,Email

...which is the headings row of the data table. Note there are 9 commas,
and the last field doesn't have a comma. Now look at a sample record
from the data table...

John,Doe,123 Main St.,Apt 101,CA,12345-6789,1234567890,,1234567891,

...where the data fields for Phone2 and Email are empty. This demos the
'proper' construction (headings row followed by records) of a CSV (or
any delimited data file) atored as plain text. This structure will
enable DAO/ADO and any other ODBC tools to read the data from the file
same as if it was reading it from a database.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion