-GUI for Users, with whatever logic is required for navigation, selection by user of desired reports & options, etc.
-MacroScheduler for execution of script(s) based on the user's work via the GUI
-pre-defined SQL & Reportwriter routines to be "called" by the various MacroScheduler scripts, against the DB.
This approach would leverage MacroScheduler for its scheduling & event monitoring capabilities (others?)
The alternative would be (I suppose) custom development of all GUI, scheduling, & event monitoring (tied to the same pre-defined SQL & Reportwriter routines as described above).
Has anyone taken this route? What are the +/- of this approach?
(development time, performance, maintenance, etc.) in the end, does it save any development time &/or $???
sharing of any & all perspectives experiences would be greatly appreciated.
