TransferSpreadsheet seems to corrupt spreadsheet

[Randy Harris]

I'm using TransferSpreadsheet to transfer data from A2K to an Excel
spreadsheet that has some pivot tables in it. It seems like it is working,
but when I open the spreadsheet, it gets an error (always asks if I want to
send a message to Microsoft). I can't figure out how to get the data into
the spreadsheet. Anyone run into this or have a suggestion?

[Randy Harris]

I've not been able to get around this problem using TransferSpreadsheet. I
cobbled around it by pushing the data over one cell at a time. It works but
is very slow relative to TransferSpreadsheet. Anyone have a suggestion how
I might speed up the process?
"Randy Harris" <ra***@SpamFree.com> wrote in message
news:oA**********************@newssvr28.news.prodi gy.com...

I'm using TransferSpreadsheet to transfer data from A2K to an Excel
spreadsheet that has some pivot tables in it. It seems like it is working, but when I open the spreadsheet, it gets an error (always asks if I want to send a message to Microsoft). I can't figure out how to get the data into
the spreadsheet. Anyone run into this or have a suggestion?

[Pieter Linden]

A quick check at AccessWeb turned up this:
http://www.mvps.org/access/bugs/bugs0024.htm

TransferDatabase Causes Page Fault If Object Exists

You may experience a GPF when trying to export an object to another
database by using TransferDatabase method. This page fault occurs if
the destination object (any valid Access object type) already exists.

The only solution at present is to use Automation to start a new
Access instance and delete the destination object before issuing the
TransferDatabase command.

Or try this method:
http://www.mvps.org/access/modules/mdl0035.htm

[Randy Harris]

"Pieter Linden" <pi********@hotmail.com> wrote in message
news:bf**************************@posting.google.c om...

A quick check at AccessWeb turned up this:
http://www.mvps.org/access/bugs/bugs0024.htm

TransferDatabase Causes Page Fault If Object Exists

You may experience a GPF when trying to export an object to another
database by using TransferDatabase method. This page fault occurs if
the destination object (any valid Access object type) already exists.

The only solution at present is to use Automation to start a new
Access instance and delete the destination object before issuing the
TransferDatabase command.

Or try this method:
http://www.mvps.org/access/modules/mdl0035.htm

Pieter, I feel I owe you a beer! Your suggestion was tremendously helpful.
I still can't use TransferSpreadsheet, however, the AccessWeb example code
used the CopyFromRecordset method, which helped. The time to transfer the
data into the spreadsheet was reduced by more than half! Thank you.

Randy Harris