and voila! ;)
Date: Thu, 24 May 2007 11:23:20 +1000
From: Boydell, Stuart [EMAIL PROTECTED]
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
Hi Stuart
Another option is to use the security features in the voc, ie Field 4 of the
Voc item. You could restrict who has access to Revise and Editor and could
even log what they are doing.
Regards
David Jordan
Managing Consultant
---
u2-users mailing list
u2-users@listserver.u2ug.org
Bottom line, dictionaries should be controlled. Period.
I lock the dicts with os-level permissions.
Just live wth EVAL restrictions. SQL not used much.
For those few cases where EVAL is important:
- references a limited copy of the full dictionary where the user can
write.
- via a 2nd
that there will
be documentation of what the system is doing after they leave the company!
Susan Lynch
F W Davison Company, Inc.
- Original Message -
From: MAJ Programming [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, May 24, 2007 11:41 AM
Subject: Re: [U2] A question of dictionaries
.
- Original Message -
From: MAJ Programming [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, May 24, 2007 11:41 AM
Subject: Re: [U2] A question of dictionaries.
I should add a comment to your post regarding the user changing a reporting
column.
This borders on a very
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
