I understand "application" security. This is the old menu based stuff
which relies upon the "average" user being set up with "limited
capabilities = *yes" to restrict them from a command line access. This is
not to be confused with the "application only" security model in which
*PUBLIC has no access the data and the only access is via programs which
adopt authority.
The problem with relying on menu based, or application, security is that
access to data via FTP, ODBC, remote command and a host of other
techniques becomes pretty wide open.
But, if you're going to run a set of routines which automatically change
all the authority on objects it would be pretty easy to migrate to
"application only" access. True, you do have to be concerned about those
users who do have a need to query data and whatnot.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.