Well, they didn't exactly dump all the security features they had in older versions, BUT - the people who did tech support kept complaining about all the Access users who tried to use their security features and locked them up so they couldn't get in, or they thought they had things locked up and discovered they were wide open if you knew what to do. So they created a new database engine (the ACE engine) in Access 2007 that didn't support the security feature, and they put the menu's for managing the legacy JET applications in obsucre places hoping we woulde never find them.

Seriously, what the folks who direct the Access development program failed to understand was that the most useful feature of the security feature is the ability to tell who the user is, so problem users can be identified and/or restricted. The developments we continue to do are all based on .MDB front-ends connecting to a SQL Server back-end - which gives us the ability to create robust applications that support large numbers of users. And we still use Access User Security to determine who gets to do what.