Security in .adp?

[Nexus]

hi, currently i have a .mdb file running with a workgroup
and different levels of users with different permission
level.

I was thinking of using Access Project (.adp) instead as
i read that it is better in a client/server application.
However, when i created the .adp file, i realise that
there the workgroup administrator function is not
available. What are the built in sercuity features for an
Access Project? Is there any way i can set different
permission levels?

 

['69 Camaro]

Hi.

However, when i created the .adp file, i realise that
there the workgroup administrator function is not
available.

When one converts an MDB database file to an ADP database file, one gives up
some of the functionality. Remember that built-in user-level security?
That's maintained by the Jet engine. You've thrown Jet away by converting
the database to use the MSDE, so the security available within Access is
gone.

What are the built in sercuity features for an
Access Project?

The MSDE is a scaled-down version of SQL Server, but it still has SQL
Server's security features, like users and roles with security permissions
on database objects. You'll want to read SQL Server's Books On Line (BOL)
to find out how to use this properly. The "Inside SQL Server" books are
excellent reference books, too.

Is there any way i can set different
permission levels?

Yes. Read the BOL. One can download it from this Web page:

http://www.microsoft.com/downloads/...b1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

 

[Nexus]

Thanks for your prompt reply I read up a little on
users and roles. But what they can offer is only security
on table level. What if i wan to prevent a particular
user from viewing a form in access?

 

['69 Camaro]

Hi.

Many Access developers create an MDE database file as the front end to
prevent users from viewing the form designs, report designs, and modules.
However, if you'd like at least _some_ of your users to view these objects,
then SQL Server security won't be adequate. You would need to place all of
your forms, reports, and modules in a separate MDB file, apply user-level
security to the forms and reports, then link to the linked tables of the ADP
file.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)