Newer Access versions throw a security warning if the VBA code is not signed and let the user disable VBA execution. The issue highlighted by hexview is able to circumvent this security-related feature.
Access 2003 on WinXP SP2 throws a security warning when I open any Access file, even one without VBA. I believe that's new with WinXP SP2.
