Donovan Bernauer
December 5th 03, 07:47 PM
Unfortunately, read permissions means copy permissions.
However, on our systems we have used NTFS and "restricted
user" rights to our advantage by disabling access to
removable storage and preventing write/change to anywhere
outside of user directories. While this prevents files
from being offloaded (assuming physical security), the
user could still zip the database and email it - but
that's what content filters are for.
Hope it helps,
Donovan Bernauer
>-----Original Message-----
>Hi all,
>
>Is there any way to stop a user from copying the front
end of an Access
>database, while still allowing him to use it. I.e. give
him read/write
>priviledges, but prevent him from using his write
priviledge to copy the
>whole file anywhere.
>
>Thanks
>
>Parviz
>
>
>.
>
However, on our systems we have used NTFS and "restricted
user" rights to our advantage by disabling access to
removable storage and preventing write/change to anywhere
outside of user directories. While this prevents files
from being offloaded (assuming physical security), the
user could still zip the database and email it - but
that's what content filters are for.
Hope it helps,
Donovan Bernauer
>-----Original Message-----
>Hi all,
>
>Is there any way to stop a user from copying the front
end of an Access
>database, while still allowing him to use it. I.e. give
him read/write
>priviledges, but prevent him from using his write
priviledge to copy the
>whole file anywhere.
>
>Thanks
>
>Parviz
>
>
>.
>