the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Progaming environment: Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010 VB based on my own environment: vb6 sp5 ASP based on my own environment: 5.6 VB-NET based on my own environment started 2007 SQL-2005 based on my own environment started 2008 MYLE YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
I would be doing the code in Access and running it either immediately before or after exporting data to Excel. Preferably before.
The data is in the form of a query. I don't have a lot of formatting options for queries. It's easier to output to an excel file, then format it later.
Before I posted my original question I tried pasting the vb code from excel into a module in access, then linking a macro to it via "RunCode". I cant seem to get the linkage right, I keep getting access errors.
"The expression you entered has a function name that Microsoft Office Access can't find"
I'd much rather call an excel macro to do the formatting for two reasons
1. It already works
2. Someone in another department has written that macro and maintains it. Every time there is a cosmetic change to their output, they can handle it themselves rather than asking me. I want to keep all the formatting issues outside of the stuff I've written.
Going back to my original question, is my syntax wrong? Is there something there I'm missing. I know you'd take a different approach but I definitely want to call an excel macro to format this excel file...