|
I have a developer on our production machine that is trying to use iNav to look at suggested access paths to build. However he can't because he doesn't have access to this file. Any reasons why I wouldn't want to let them? Only remote thing I can think of is the old "security by obscurity" concept that if he browses this file then he may see a recommendation to build an access path over a file named WAGES in a library called PAYROLL and that might inspire him to look harder at a way to get into that file. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.