nVision Macro Security and making it "Safer"...
Hi all,
I'm wondering if anyone has any best practices regarding securing nVision Macros? We are concerned that someone may develop a destructive VBA Macro/Script, and given nVision runs on the process scheduler as an Admin account, we're wondering about others experiences on reviewing macros, locking down security for the process scheduler, adding trusted certificates to Excel, etc.
Just looking for in general, others experience how to make macro deployment as part of nVision Reporting "safer"....both from a development and production standpoint.
Thanks!
Robert