Re: How to set up read-only accessibility to an existing .mdb
- From: "Br@dley" <n0mail@xxxxxx>
- Date: Wed, 27 Jul 2005 23:13:58 GMT
TechBoy <ronnolan@xxxxxxx> wrote:
> RE: Access 2002 SP3
>
> I have an app "App1.mdb" that has internal security built-in via a
> table: tblSecurity. In this table a match is obtained to see if they
> are authorized to use the app.
> This application has no Jet security being used ("Users/Groups", etc.)
>
> One of the requirements was to hide the DBWindow completely from the
> users, which works fine and the DBwindow is secure from all users.
> Another requirement for App1.mdb: the users need to create ad-hoc
> reports in the report designer area of this app.
>
> Is there a way to create a second .mdb "App2.mdb" that links to the
> tables in App1.mdb, but with purely read-only capability?
>
> Any counsel is appreciated.
>
> Thank you.
To do it properly you'd need to implement obviously workgroup security.
--
regards,
Bradley
A Christian Response
http://www.pastornet.net.au/response
.
- Follow-Ups:
- References:
- Prev by Date: Re: DCount, by customer
- Next by Date: Re: Permission problems with Access and SQL
- Previous by thread: 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
|
