[AccessD] Setting data into and getting data from Named Range s

Hi Gustav,

Yes, MS Excel worksheet is limited to have 65536 rows and 256 columns
AFAIK...

"large recordset" is a relative term - it all depends of course - it
should be small enough to fit a certain application reqirements for
processing speed - for one application it can be 10 rows, for another -
10000 rows....

As for linking MS Excel worksheet range as an MS Access table - as far
as I understood the main question/task to solve of this thread was to
NOT use linked MS Excel worksheets because of licensing troubles...

Shamil

----- Original Message ----- 
From: "Gustav Brock" <Gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Tuesday, January 24, 2006 1:14 PM
Subject: Re: [AccessD] Setting data into and getting data from Named
Range s


> Hi Shamil
>
> That's a nice and clean solution with the disconnected dataset.
Thanks.
>
> But what is a "large recordset"? Isn't Excel limited to 65536 rows?
> Would it be faster to link such a large range as a table in Access?
That's what I use but I've never handled recordsets this way with more
100 rows.
>
> /gustav
>
> >>> shamil at users.mns.ru 24-01-2006 01:03 >>>
> John,
>
> Have a look here is a generic code to get data to ms excel worksheet
> from MS Access database and to save data to MS Access db from ms excel
> worksheet using disconnected ADO recordsets. This sample uses arrays
> because an MS Excel range value is in fact a variant array. It
shouldn't
> be used with very large source recordsets but as far as I understood
you
> will not have such recordsets...
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com