[AccessD] Fwd: Re: Is it better to call Excel Macro from access, or manipulate from Access?

[David McAfee]

I want to keep it in Access because the report is just one step of many
that are ran from a menu system that I made.
I really am trying to dumb it down for the user as much as possible.

Press a button and a nicely formatted Excel file is placed in a certain
directory.

Last night, I did find some useful links:

http://datapigtechnologies.com/blog/index.php/running-an-excel-macro-from-access-or-another-excel-workbook/

http://bytes.com/topic/access/answers/902069-export-queries-excel-specific-sheet-specific-range

http://www.access-programmers.co.uk/forums/showthread.php?t=249829

I think I can piece together something over the weekend that resembles a
rube-goldberg project :P

Thanks again,
David

On Fri, May 15, 2015 at 1:26 AM, Bill Benson <bensonforums at gmail.com> wrote:

> Some opinions from additional excel experts David. I also by just gut
> feeling would have coded this from Access.
>
> On the flip side I might have treated Access like a backend and written
> similar queries and transformations you might be running in Access with ADO
> and put the project in Excel, if possible.
> ---------- Forwarded message ----------
> From: "John Nurick" <john.nurick at nurick.net>
> Date: May 15, 2015 4:22 AM
> Subject: Re: [AccessD] Is it better to call Excel Macro from access, or
> manipulate from Access?
> To: <EXCEL-L at peach.ease.lsoft.com>
> Cc:
>
> +1. Also, to my tidy mind it always feels neater to have all the code in
> the
> same project (not counting add-ins).
>
> -----Original Message-----
> From: Microsoft Excel Developers List [mailto:EXCEL-L at PEACH.EASE.LSOFT.COM
> ]
> On Behalf Of Rory Archibald
> Sent: 15 May 2015 09:18
> To: EXCEL-L at PEACH.EASE.LSOFT.COM
> Subject: Re: [AccessD] Is it better to call Excel Macro from access, or
> manipulate from Access?
>
> Unless there is a need for the macros to exist in Excel (e.g. they may need
> to be run again separately to the original Access processing) I see no
> benefit in having them in Excel. I'd do everything in Access. The process
> itself sounds unnecessarily complicated to me - a simple CopyFromRecordset
> would avoid the need for creating and deleting header rows altogether.
>
> --------------------------------------------------------------------------
> The EXCEL-L list is hosted on L-Soft international's LISTSERV(R) software
> running on Microsoft Windows Server 2008 R2. For subscription/signoff info
> and archives, see http://peach.ease.lsoft.com/archives/excel-l.html .
>                              COPYRIGHT INFO:
> http://peach.ease.lsoft.com/scripts/wa.exe?SHOWTPL=COPYRIGHT&L=EXCEL-L
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>