ADO GetString

[Mike Kenzie]

I have noticed that if you are trying to format a large recordset in VB or
VB script (say around 300 records), the GetString function can be substantially
faster than looping through each record and formatting it that way. Are
there any downsides to using the GetString function performance or scalability
wise?

Mike Kenzie

[Bill Vaughn]

I discuss this at some length in the new book (mentioned eariler). GetRows
or GetString returns a variant array or a "pseudo" delimited string. Ok,
now that you have the array or string, now what? You lose almost all (or
all) of the DDL information but that might not be a problem--you still have
the original Recordset. You do have the data, but to display it you have
to figure out how to do this yourself. The Clip property can accept a delimited
string, but the MSHFlexGrid.Recordset is faster and takes the ADO Recordset
object directly. If you're considering passing the data from tier-to-tier,
a DS is not a bad choice. It's ANSI (as opposed to Unicode), it's lightweight
(no DDL), but it assumes the target knows what to do with it. There are lots
of other tradeoffs discussed in the book...

hth
bv



"Mike Kenzie" <mkenzie@solutechinc.com> wrote:
>
>I have noticed that if you are trying to format a large recordset in VB
or
>VB script (say around 300 records), the GetString function can be substantially
>faster than looping through each record and formatting it that way. Are
>there any downsides to using the GetString function performance or scalability
>wise?
>
>Mike Kenzie