Security in 2007

[Guest]

I have a fe/be application in Acc 2003 and I am starting to look at Acc 2007.
There are some new features in 2007 that I would like to incorporate into
the app. One of the features NO LONGER AVAILABLE in native 2007 is user
level security (ULS).

I was using ULS to keep users out of design mode on forms, query etc. If
the FE is opened by a user (as opposed to a developer as defined in ULS) the
app made sure that it was being run in run time mode only. It also prevented
anyone with Access using the standard ADMIN user from opening the fe or be.
While I realize that a power user who has the will could break this, it works
pretty well for my environment. If I convert to 2007 is there a way (in
code) to make sure that a user cannot get into design mode. I guess I could
check that if the current db is an mde (accde in 2007 ) that it runs with
/Runtime option.

Any thoughts or other tricks to keep users out of design mode? Has anyone
converted to native 2007? Any horror stories?

 

[Keith Wilby]

I have a fe/be application in Acc 2003 and I am starting to look at Acc
2007.
There are some new features in 2007 that I would like to incorporate into
the app. One of the features NO LONGER AVAILABLE in native 2007 is user
level security (ULS).

I was using ULS to keep users out of design mode on forms, query etc. If
the FE is opened by a user (as opposed to a developer as defined in ULS)
the
app made sure that it was being run in run time mode only. It also
prevented
anyone with Access using the standard ADMIN user from opening the fe or
be.
While I realize that a power user who has the will could break this, it
works
pretty well for my environment. If I convert to 2007 is there a way (in
code) to make sure that a user cannot get into design mode. I guess I
could
check that if the current db is an mde (accde in 2007 ) that it runs with
/Runtime option.

Any thoughts or other tricks to keep users out of design mode? Has anyone
converted to native 2007? Any horror stories?

If you keep to the mdb file format then you can carry using ULS.

Keith.
www.keithwilby.com

 

[Guest]

Thanks Keith for the feedback. I understand that I can keep it as an mdb and
have ULS function properly, however some of the new native 2007 offering will
not function with a prior version format. At least as I understand it.

I was looking for the ability to replace the ULS in native 2007 and still
keep users out of design mode for tables, properties and the like.

 

[Joan Wild]

Have a look at Garry Robinson's article at
http://msdn2.microsoft.com/en-us/library/bb421308.aspx

You can roll your own security. See the following for some guidance:
http://www.pdtltd.co.uk/pdtl/Access2007/Access 2007 vPPC.pdf
or
http://www.utteraccess.com/forums/s...373275&page=1&view=collapsed&sb=5&o=&fpart=1I

 

[Guest]

Thank you Joan for your references! I am amazed that with all the blowback
Microsoft hasn't had second thoughts about this issue.

 

[Keith Wilby]

Thanks Keith for the feedback. I understand that I can keep it as an mdb
and
have ULS function properly, however some of the new native 2007 offering
will
not function with a prior version format. At least as I understand it.

I was looking for the ability to replace the ULS in native 2007 and still
keep users out of design mode for tables, properties and the like.

Sorry, I misunderstood. This will be a major PITA for me when we get Office
2007 but probably not for another 5 years at least (we only got 2003 last
year).

Keith.

 

[David W. Fenton]

I understand that I can keep it as an mdb and
have ULS function properly, however some of the new native 2007
offering will not function with a prior version format. At least
as I understand it.

Which functionality that you need won't work? The only thin I can
think of is new data formats, which would be just the multi-value
field (which I would never use, anyway). What else is there?