D4E SQL - Transform VBA into CPS230 governance
HAVE YOUR VBA WITHOUT THE HASSLES OF XLAM/XLSM? It's like having your cake and eating it too!
With D4E SQL in Data Mart for Excel, we demonstrate how we provide CPS230/220 governance to existing user VBA codes that are scheduled for removal, due to adverse findings as risky.
Files used in the video:
https://www.datamart4excel.com/downlo...
#cps230 #cps220 #excelautomation #vba #riskmanagement #excel
***Some technical gotchas in this video:
1. Enterprises may block Level 1 solutions using hardened registry settings, for example:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Security
AccessVBOM = 0 → blocks programmatic creation/injection of VBA code.
In these environments, Level 2 must be used.
If Level 1 is not blocked, VBA in cells can be encoded for further protection.
2. Level 3 uses a 3rd-party compiler to further protect XLAM files (VBACompiler)
Why not just convert all UDAs/VBAs directly to COM DLLs?
Because a COM DLL mainly provides code protection + version control.
If it is still run manually, it remains single-person dependent, with no audit or orchestration, so operational risk remains high.
When executed through D4E orchestration, every run becomes repeatable, auditable, and not single-person dependent.
3. Although CPS230/220 is for Australia only, there are regulations basically covering the same problem in US (SOX, SR 11-7, FFIEC Handbook, OCC), UK (PRA SS1/23, PRA SS2/21, BCBS 239) and EU (EBA, DORA).
#excelautomation #excelformula #cps230 #governance #sox #dora
#excelesports #mewc #financialmodeling #dataanalytics