Don't you think the better solution is to keep the data in Access. You can
always use the menu option in Access to see the data in Excel? If the
customer is not happy, then simply perform the export from Access to Excel
once and give him the excel file. Don't tell the customer the source is
really an Access file.

Access Menu.
Tool - Office Links - Analyze it with Microsoft Excel

"mono" wrote:

thanks for your reply!
the client is not happy with the fact that there are two files. And they
want to use Excel to see the data, as they might want to do further
calculations in Excel.
The macro in Excel only GETs data from the Access database, so Access is
only the data container, because there's too much data to have everything in
an Excel Workbook. (And there's no need to write TO the Database, the
database is "read-only"...)
hope this makes it a bit clearer

"Joel" wrote:

Have you thought about writing the macro in ACCESS rather than Excel? Is the
Customer not happy with the fact there arre two files, or is the problem with
the data entry being in Access and the Output being in Excel?

We need a little bit more explanation of what the customer requirements are
to determine the best solution. I think just adding a Front End (macro in
excel) for writing the data into Access is may be the right solution.

"mono" wrote:

hello,

I did a small excel vba program that displays data from an access database.
The access database is used as a data container only. The client is now not
happy with the fact that he always has to take care of two files (the XLS and
the MDB), he'd like to have everything in one file. Is there a way to have
the whole database included in the excel workbook (e.g. as OLE object)? I
tried the OLE thing, but I was not successful...

using office 2003, by the way.

thanks a lot!