|
Hee hee hee! "Screw sarbox!" By the way, have you heard the rumblings that one of the unintentional side effects of sarbox is that some large companies are considering going private? Well, if you know which files the user run queries over, you can limit access to other. If on the other hand they can run queries over anything, then you have huge issues of database maintenance. In any case, I have run into few operations that have quite as fluid requirements as yours seems to have, so while locking down the system might not work for you, it is still a viable business option for others. Joe > From: rob@xxxxxxxxx > > We're private - screw sarbox. > > I don't think we changed any existing files for that project. Especially > any files that the users run queries over, like IIM, etc.
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.
midrange.com
