|
> From: rob@xxxxxxxxx > > You are probably right on some of your more secure files, (but isn't that > what you said?). And granted some data relationships need to be fully > understood to make sound business decisions. Actually, I think we've come to what is probably a reasonable middle ground. For secure files, we have a solution: I/O modules with a firewall trigger. For query-accessible data, you can still provide I/O modules and a firewall trigger for updates, and then grant read access via profiles. These can be added as supplemental group profiles on the users that need the access. And I'll even go so far as to say that basic referential integrity rules can still be implemented via the database, provided it is commented in the I/O module as well (you should probably have a program to create the requisite relationships as needed). Joe
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.