Access not releasing Excel

[sausage31]

I'm exporting some data to excel but am having trouble getting Access
to 'release' Excel.

What i want to achieve is to open excel, export some data then leave
excel open so that the user can them manipulate the excel spreadsheet
however they wish. The problem is that Excel instance is still open
even when the user has finished with the spreadsheet and manually
closed the application.

How can i break the tie to Excel but leave it and the exported
spreadsheet open?

As a side issue which is the "better" (preferred) way to export the
data - use the transferspreadsheet method or copy from a recordset?

Many thanks

Simon

[Keith Wilby]

si**********@dynexsemi.com (sausage31) wrote:

As a side issue which is the "better" (preferred) way to export the
data - use the transferspreadsheet method or copy from a recordset?

I use ODBC to transfer data to Excel, but if you're using code, do you
close all recordsets and set them to = Nothing?

ie

rs.Close
Set rs = Nothing
db.Close
Set db = Nothing

[James Fortune]

Keith Wilby <ke*********@AwayWithYerCrap.com> wrote in message news:<Xn************************@10.15.188.42>...

si**********@dynexsemi.com (sausage31) wrote:

As a side issue which is the "better" (preferred) way to export the
data - use the transferspreadsheet method or copy from a recordset?

I use ODBC to transfer data to Excel, but if you're using code, do you
close all recordsets and set them to = Nothing?

ie

rs.Close
Set rs = Nothing
db.Close
Set db = Nothing

This correlates to what I've read. On http://www.OutlookCode.com one
of the articles talks about how not releasing every single Automation
object you Set such as a Worksheet will cause Outlook to stay open. I
think this was for Early binding. It sounds like Excel is the same
way. As far as exporting the data to Excel it depends on what you're
doing. In some cases just having Access link to the Excel spreadsheet
and then running an update query is the easiest way to change the
data. Transferspreadsheet looks pretty efficient. I've never used
it, though, since I like fooling around with the model :-).

James A. Fortune