Re: How to set up read-only accessibility to an existing .mdb
- From: "Rick Brandt" <rickbrandt2@xxxxxxxxxxx>
- Date: Thu, 28 Jul 2005 13:01:05 GMT
RLN wrote:
>>> To do it properly you'd need to implement obviously workgroup
>>> security<<
>
> I have never worked with Jet security before. Is it pretty
> straightforward or are there some resources that would be helpful in
> walking me through setting it up?
> Reason I ask is, I have my application broke up into 2 .mdb files:
>
> MyApp.mdb and MyAppData.mdb.
>
> The data version has all the tables only, while the other has all the
> forms, controls, modules, report, etc.
>
> MyApp.mdb has links to tables in MyAppData. Do I set up the workgroup
> security in MyApp.mdb or MyAppData.mdb for the users to have pure
> "read-only" accessibility to all table for creating adhoc
> reports/queries?
If you go with User Level Security you would need it on BOTH files.
Security is controlled by the workgroup file and there is only one of those
per Access session so the file you open directly and any file that is has
links to are all affected by it.
If you want ALL users to be read only you can simply place the data file in
a folder where they have read-only permissions. If you want some to be
limited to read only and others to be able to edit data, then User Level
Security is the way to go. Network permissions cannot be used for that.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
.
- Follow-Ups:
- References:
- Prev by Date: Re: How to set up read-only accessibility to an existing .mdb
- Next by Date: Re: Problem with Embeded Querys
- Previous by thread: Re: How to set up read-only accessibility to an existing .mdb
- Next by thread: Re: How to set up read-only accessibility to an existing .mdb
- Index(es):
Relevant Pages
|