Re: Copy Contents of Recordset to a table

"pmc1" <paulc05@xxxxxxxxx> wrote in news:1148917674.126685.241810
@j73g2000cwa.googlegroups.com:

I tried this and I'm hoping there is a quicker way to achive this. The
remote DB is on a remote share and connection speeds aren't create. one
of the uses of the DB on the remote share is to serve as a central
point for dynamic tables that are used in excel by variuos users in
various locations. Using Recordsets I pull approx 7000 rows of Data
from the remote db directly into an Excel table on the client. This
takes approx 45 second.

When i try to refresh the linked table in access this takes over a
minute so would a recordset not be better in this instance?

Have you tried DoCmd.TransferSpread***?

While this command is not fast its use would do away with intermediate
databases and intermediate recordsets. You should be able to just create an
instance of an access application, open the remote db with that (nothing
will show), do the Transfer (AcExport) and close the application instance.
TTBOMK this will create the work*** in the existing Excel file, or write
over it if it (the work*** not the file) already exists.

In many years of working with Access I can think of only two cases where
recordset manipulation may have been the best way; one was because I was
using someone else's *** normalization scheme and the other, my own, I
ditched and retreated to user-defined SQL Server function; it was slower
but cleaner.

999 times out of a 1000
RecordSet = Inefficency

Of course, I may totally misunderstand what you are trying to do.

--
Lyle Fairfield
.