There is a debate among our security people. Some say that MS Access is a
software app, others considered a system and needs to be CNA`d. I say its a
software app. Any thoughts.
I'm a bit unclear on what constitutes a "system", so I really can't
address that directly. However, I tend to look at Access as three things
in one package:
1) A database engine
2) An IDE
3) An application
1) Consider SQL Server. It's a database engine, and you certainly can't
hand it off to a user and expect them to find their way around the
tables and rows.
2) Consider Visual Studio. It's an IDE and you can write code to build
an application with it. It doesn't come with a database engine... at
least not without you taking step to actually include or refer to it. It
also can't run an application as an application. You would use it to run
it in debug mode to test/step through the code but not to actually use it.
Access does all of that in the same package - but of course this assumes
that the user is the developer which is not always the case here - more
often than not, the user is here to use it as an application that's
developed by someone else (even if not officially a developer - could be
just a power user or the "most tech savvy guy in the office").
Back to the question - if I were to want them to treat Access as an
application, I'd think about distributing MDE/ACCDE files instead so it
will in fact act more like an application and less than an IDE. That
won't save the developer's machine from needing to be auditing because
we still need the full version of Access (and thus the IDE capability)
to develop the applications. (That's assuming they would treat an IDE as
a "system"... how do they handle Visual Studio and software supporting
SQL Server (e.g. SSMS & BIDS?)
My $0.02 FWIW.