A2007 User Level Security

TKnight

Registered User.
Local time
Today, 22:04
Joined
Jan 28, 2003
Messages
181
Does anyone know why A2007 has completely removed the User Level Security (ULS) from it's new DB format?

It seems crazy not just for security but how easy it is to create user-specific functions (audit trail) etc. with Application.CurrentUser

I know it will remain the same for <=2003 MDE's etc. but that basically means I can't upgrade to develop in 2007 because I rely on ULS way too much. And what if they don't put it back? Will we really have to go old skool and write our own user/security functions?

Shame because I was really looking forward to getting my hands on the E-mail form and auto-update with outlook!

Am I missing something?

Thanks,

Tom
 
To my knowledge ... you got it. I don't have them marked, but there are articles out there where they tried to justify that position on the change, I didn't like it.

Just like you stated, for my '07 user security, I had to create user tables and groups, and modules to control the access levels.

=[
-dK
 
I'm sorry but that is just RIDICULOUS!!!

I've just been reading up online and I haven't seen a single developer who seems to be in favour of ditching ULS. One official Access blog got bombarded with protests as early as 1995 but it seems like they didn't listen.

Fair enough - change the name so as not to imply security, call it User Level Functionality instead but don't drop it all together.

What really hacks me off is that it's punishing the people that Access should really be embracing (i.e. serious users) and playing into the hands of people who don't consider it a 'proper' database.

I work in a small team who develop almost exclusively in Access. We create high functionality bespoke systems that basically prop up our off the shelf systems because no major developer can be bothered to create stuff to the level of detail that we want it. Why - because it takes too long and costs too much so they don't do it. That's where Access rules to be honest. Yeah we use Oracle for our bank transfers etc. but the real "brain" of our operations is virtually all created/managed with Access. A recent audit by a government department credited us with having one of the most joined up financial systems in the country - guess what does the "joining".

The steps that Microsoft seem to be taking for A2007 are just going to make it that much harder for us to justify our choice of development application and i'm sure will see a lot of developers off for good!

I really hope it backfires on them big-time and they have no choice but to re-implement...

Tom
 
... that basically prop up our off the shelf systems because no major developer can be bothered to create stuff to the level of detail that we want it. Why - because it takes too long and costs too much so they don't do it. That's where Access rules to be honest. ...

Well said!

-dK
 

Users who are viewing this thread

Back
Top Bottom