One approach would be to set up separate accounts for privileged vs.
non-privileged users.  That would give you two VOC files, and the paths
to the data could be different for some or all of the files.

Another approach is the following:

In UniData this could be done by using environment variables, and
assigning the variable with different values for some users than for
others.  For example:

F
@ENVVAR/PRIVATEFILE
D_PRIVATEFILE

User "A" (privileged) could have it set to C:\private.  User "B" could
have it set to "."

I don't know how much trouble that is to set up for windows users
though.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Augusto Alonso
Sent: Wednesday, November 28, 2007 1:46 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] Need to partially hide a file

Hi all.

Can someone tell me if it is possible?
I'll explain the scenario:
We need to hide some private data (customer personal data) in order to
fit with our Private Data Protection Law.
But only  for some users, the others, they need to have full access.
Our app is complex enough to modify the source code.
So, our ideal sollution would be making a "dynamic" File Entry VOC, that
will look like this:

For Non-privileged users:

    >CT VOC PRIVATEFILE

         PRIVATEFILE
    0001 F
    0002 PRIVATEFILE
    0003 D_PRIVATEFILE



And for privileged users:

    >CT VOC PRIVATEFILE

         PRIVATEFILE
    0001 F
    0002 C:\private\PRIVATEFILE
    0003 D_PRIVATEFILE

so that, the rights could be defined at O.S. level, and the app will
allways open a file (the private one or the public one)

The problem is that I can't figure out how can I do a VOC entry dependig
on the particular user.
Or even, if it is possible...

TIA.

Regards,
Augusto Alonso
[EMAIL PROTECTED]
www.quiter.com
-------
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/

Reply via email to