We are implementing source control here and I was wondering, in light of data protection and source control best practice and the US list members experience of Sarbanes-Oxely, if anyone is currently running their production systems using OS level (D_filename) read-only dictionaries. I know that EVAL and SQL NEXT.ACCUMULATOR statements which write back to the dictionary will fail but have you encountered any other gotcha's? Or if you have contemplated the idea of locking dictionaries, but abandoned it, why? I'm also curious to find out (as Australia legislation has been influenced by it) what the implications as far as SOX is concerned where a user can potentially [if they gain access to a writable dictionary] change a reporting column, or doesn't it go that far? Cheers, Stuart Boydell
********************************************************************** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ********************************************************************** ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/