Re: Will It Be Fixed?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

It also says, "To have multiple people use the database but with different
data access privileges, the recommended practice was to move this data to a
centralized service like SQL server or SharePoint lists." Thus, it appears
to me that Microsoft is moving the security model away from "Jet" (whatever
it ends up being called) to SQL Server and SharePoint. I don't think they
will be doing any improvements on the Jet security model, although it will
still be available for backward compatibility.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



"StepUP" <StepUP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4D73C7DC-09F3-41D1-9BDE-952CAEC17901@xxxxxxxxxxxxxxxx
Ahh but just before that sentence it said "To help promote using truly
secure
user-level security..."

and then

"We believe that the security work in Access 12 will both make the product
more secure through things like the improved encryption and clearer
user-level security"

Doesn't seem that clear to me!

"Joan Wild" wrote:

Well I thought it was pretty clear. Quoting from the blog...
"ACE will no longer support the JET concept of user level security for
new
file formats"

--
Joan Wild
Microsoft Access MVP

StepUP wrote:
Hmmm...interesting. But it still leaves the question up in the air.

It seems to say...."Yes, there will be better security", but doesn't
fill in the details. Still unanswered..."Will there still be User
Level Security?".

This blog was back in October...anyone know of an updated status?

Thanks Jeff.





.

Relevant Pages

  • Re: Access 2003
    ... It should read SP 8 for Jet 4.0 in the appropriate places. ... "Jeff Conrad" wrote in message: ... I still do not understand why Microsoft creates such issue to all ... >> appear so I cannot turn it to sandbox mode to avoid security warning. ...
    (microsoft.public.access.setupconfig)
  • Re: setting a password on a button on the switchboard
    ... Could you send me the sample database for the fourth option (4. ... > Security in an Access database can probably be broken down into two big ... > points about being easier than User Level Security, ... > What type of data are you trying to protect? ...
    (microsoft.public.access.forms)
  • Re: Create a Form Password
    ... Let me provide my *few* thoughts about Access Security. ... Security in an Access database can probably be broken down ... into two big categories: home-grown security or Access ... User Level Security is using ...
    (microsoft.public.access.forms)
  • Re: setting a password on a button on the switchboard
    ... Let me provide my *few* thoughts about Access Security. ... Security in an Access database can probably be broken down into two big categories: ... User Level Security. ... What type of data are you trying to protect? ...
    (microsoft.public.access.forms)
  • Re: A2K Splitting and Security
    ... to the user's log-in name which would map him/her to a security level. ... on a query that used the underlying table in the BE database. ... > You don't really need user level security if you don't care about assigning ... >> incorporate the idea of the complied mde type file. ...
    (microsoft.public.access.tablesdbdesign)