Hello, I am using Excel XP with Win 2000 and ADO 2.5.

1) When converting an ADO recordset into a string using "GetString", does
anyone know of any bugs, row limitations, length or size restrictions, etc.
with this method?

I'm considering using this method for importing data when there is too much
to fit into an Excel sheet. Alternatively, I will port the data into a CSV
text file and I just wanted to know how stable this method is. I would use
the syntax shown below:

rsADO.GetString(adClipString, , ",", vbCr)

2) Also, does anyone know if this method automatically (internally)
surrounds each column with double quotation marks? If not how can I get it to
do this? Please illustrate the syntax.

Thanks much in advance.

quartz wrote ...

I'm considering using this method for importing data when there is too much
to fit into an Excel sheet.
Alternatively, I will port the data into a CSV text file

GetString may not be the best way of creating a csv file. Jet's
SELECT..INTO syntax is better and puts in the double quotes where
appropriate.

If your ADO is a Jet data source (.xls, .mdb, etc) you just need to
insert an INTO clause e.g. if your sql text looks like this:

SELECT MyTextCol
FROM MyTable;

then change it to something like this:

SELECT MyTextCol
INTO
[Text;HDR=YES;Database=C:\MyFolder\;].MyFile#csv
FROM MyTable;

If you are using a non-Jet data source you may be able to use the same
trick by opening a connection to a Jet source (e.g. a nonexistent
..xls) and putting an odbc connection to you actual data source in the
sql text e.g. for SQL Server data source:

SELECT lname AS MyTextCol
INTO
[Text;HDR=YES;Database=C:\MyFolder\;].MyFile#csv
FROM
[ODBC;Driver={SQL
Server};SERVER=MYSERVER;DATABASE=pubs;UID=***;Pwd= ***;].employee;

Jamie.

--