I should add a comment to your post regarding the user changing a reporting column.
This borders on a very slippery topic regarding the user's access to the system. In my travels, many systems prevent their access to TCL. Those that allow access only give the users a very, very limited set of commands like LIST and SORT and perhaps SELECt but never EDIT or BASIC etc. Plus the user's natural inhibitions prevent them from learning (retaining) what they may see us typing. So I guess my question is what kind of 'user' could actually change a reporting column to begin with. In many of my clients' systems there are formal, menu-driven reports with specific indicators in the headings for report identification. The users who make their own English report never, never use HEADING so that would be my first sign of a renegade report. I don't use EVAL or other live dict items and I can't imagine the most serious non-MV user crossing over that line. We programmers, having the keys to the entire castle, sometimes feel that the users are only one small step behind us. Everytime I think that they're near me, I'm reminded of how contained they actually are. For over a quarter of a century I've been trying to show users the simplicity of creating their own reports in English. I've found that you can lead a horse to water but you cannot make them drink. I've seen users decline retaining education after attending Crystal Reports classes, Excel Classes, Powerpoint classes and even MS Access classes. I don't think they will take a liking to our dictionaries. My 2 cents Mark Johnson ----- Original Message ----- From: "Boydell, Stuart" <[EMAIL PROTECTED]> To: <u2-users@listserver.u2ug.org> Sent: Wednesday, May 23, 2007 9:23 PM Subject: [U2] A question of dictionaries. > 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/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
