B
Bob Calvanese
I have been reading a lot of posts and see a lot of hard coding as well as
macro's within excel itself.
I was once a reporting automations developer for a telemarketing company. I
was responsible for all financial reporting and there was another guy who
did all the insurance reporting automation.
All of our reports where in excel and where all custom templates sent to us
by our clients. We inturn turned the templates into the reports and
automated them so the reporters could run them.
My approach to this was to find a way to control the automation out side of
excel using VB6. It took a year, but I developed a system that used the
template as a map that my system would scan. It would then create a set of
tables that would hold the information needed to get the data from oracle,
open the report file, and populate the report. I used made up key words that
the reporters could understand and key into their report template where they
would normally input the data. This enabled them to set up their reports
into my system without having to know anything about programming. Once they
set the report up they could run it every day with the click of a button. If
the client made changes to the template, the reporters would merely make the
same changes to their template, rescan it, and it would be ready to run
again.
The guy who automated the insurance reporting had a different approach. He
took each report and wrote macro's in excel for each one. This turned into a
nightmare for him, because he had to maintain all the reports indavidually,
and when the client wanted changes he had to re-code the report each time.
Needless to say he became stuck in his position because he was the only one
who could maintain all of his propriatary reports.
Because my system eliminated the need for my position (aside from
maintaining one system), I was able to move into the programming department.
After the other guy left (he put himself in a position where he had no where
else to go), I took all his reports, stripped out his macro's, and scanned
them into my system.
The point to all of this is... If you have a lot of excel automation. Do not
use macro's within excel to do it. You will wind up with a nightmare of
propriatary code to maintain, and you will be the one stuck with it (unless
that is what you want).
If you only have a few automation things to do, then macro's are great.
Just a suggestion.
macro's within excel itself.
I was once a reporting automations developer for a telemarketing company. I
was responsible for all financial reporting and there was another guy who
did all the insurance reporting automation.
All of our reports where in excel and where all custom templates sent to us
by our clients. We inturn turned the templates into the reports and
automated them so the reporters could run them.
My approach to this was to find a way to control the automation out side of
excel using VB6. It took a year, but I developed a system that used the
template as a map that my system would scan. It would then create a set of
tables that would hold the information needed to get the data from oracle,
open the report file, and populate the report. I used made up key words that
the reporters could understand and key into their report template where they
would normally input the data. This enabled them to set up their reports
into my system without having to know anything about programming. Once they
set the report up they could run it every day with the click of a button. If
the client made changes to the template, the reporters would merely make the
same changes to their template, rescan it, and it would be ready to run
again.
The guy who automated the insurance reporting had a different approach. He
took each report and wrote macro's in excel for each one. This turned into a
nightmare for him, because he had to maintain all the reports indavidually,
and when the client wanted changes he had to re-code the report each time.
Needless to say he became stuck in his position because he was the only one
who could maintain all of his propriatary reports.
Because my system eliminated the need for my position (aside from
maintaining one system), I was able to move into the programming department.
After the other guy left (he put himself in a position where he had no where
else to go), I took all his reports, stripped out his macro's, and scanned
them into my system.
The point to all of this is... If you have a lot of excel automation. Do not
use macro's within excel to do it. You will wind up with a nightmare of
propriatary code to maintain, and you will be the one stuck with it (unless
that is what you want).
If you only have a few automation things to do, then macro's are great.
Just a suggestion.