Question Using *.mdb within Access 2007/2010 over the long run.....

[sjl]

Hi,

I have a 2003 *.mdb that I have user-level security on. I just managed to tweak the password shortcut so that it'll open in Access 2010(2007). I've tested it some and the user-level security seems to be in tact.

My Question: Have any of you had a longer-term experience with using an *.MDB inside the Access 2010/2007? Wondering if there may be some issues down the road I am not thinking of/testing.

We have 13 users who have been read-only users and 2 who have had full data access while working under ver 2003. However, now I.T. is wanting to know if they can push out 2010 on all machines and remove version 2003.
Thanks for any input here....

 

[HiTechCoach]

I think that one of the reason Microsoft dropped the built in User Level Security (ULS) in the new ACE ( accdb) database engine for Access 2007/2010 is due to the lack of use. Also that is really is not secure and world take to much effort to make it work properly.

You probably are one of the few heading into this new frontier.

 

[Banana]

Because .mdb is still considered a native format, if not preferred, it's equally reasonable to expect that user-level security will continued to be supported at least for 2007 + 2010. No guarantee on beyond 2010.

 

[davsch]

sjl,

Can you elaborate on how you tweaked your shortcut so you can open a 2003 .mdb in 2010?
I need to be able to run existing .mdb's in 2010 while some users are still on 2003. At least until we totally convert.

Is this possible?

I currently have multiple .mdb's that are managed via the wrkgadm.exe and looking to see how you successfully worked out that issue before you finally converted completely to 2010. Exactly what was your shortcut tweak?

Regards,

Dave

 

[boblarson]

There is no tweak necessary. You can open and use an mdb file from 2010. You can, if you are using an mdb file, use the User Level Security. It is just as it is in any other version.

You can NOT use User Level Security with an ACCDB file.

 

[spikepl]

#1 Entirely OT: Kudos to your IT-people for asking and showing concern for a disowned application

 

[davsch]

Bob,

Thanks for the quick response.
Yes, I am able to open .mdb's in 2010 that do not have user level security in 2003, but when I try to open a .mdb in 2010 that does have uls set, I cannot get into the database. I receive the error message:

"You do not have the necessary permissions to use... my .mdb... Have your administrator or the person who created this object establish the appropriate permissions for you."

It does not even give me the opportunity to enter a user name and password that has permissions, it just goes right to the error message.

When using 2003 and with a new client or fresh PC install, I would have to run wrkgadm.exe and join. ???

I am guessing I am missing something very simple.

Dave

 

[gemma-the-husky]

i am not clear on this, either

if A2010 has deprecated ULS - does this mean there is no longer a system.mdw at all? or does it mean there is only a system.mdw that cannot be amended?

i haven't checked - but maybe there is a trust centre setting to ignore ULS?

-----
with respect to your sysadmin people - why do they need to remove A2003 at all. Surely they can retain both A2003 and A2010. Can't do any harm.

 

[boblarson]

i am not clear on this, either

if A2010 has deprecated ULS - does this mean there is no longer a system.mdw at all?

No, that doesn't mean that. If you use the MDB file format, you can still create an MDW file, use an MDW file and modify an MDW file (through the Security Manager).

i haven't checked - but maybe there is a trust centre setting to ignore ULS?

Nope, there isn't.

with respect to your sysadmin people - why do they need to remove A2003 at all. Surely they can retain both A2003 and A2010. Can't do any harm.

It isn't good to use multiple versions of Access as it can cause problems. I would suggest that you either use one or the other. But if you have to use both, then not only should each person have their own frontend file, but each version have its own separate frontend file compiled on that version, due to the major differences between 2010 and 2003 (and especially with the SP1 issues around ADO).

Yes, I am able to open .mdb's in 2010 that do not have user level security in 2003, but when I try to open a .mdb in 2010 that does have uls set, I cannot get into the database. I receive the error message:

"You do not have the necessary permissions to use... my .mdb... Have your administrator or the person who created this object establish the appropriate permissions for you."

It does not even give me the opportunity to enter a user name and password that has permissions, it just goes right to the error message.

When using 2003 and with a new client or fresh PC install, I would have to run wrkgadm.exe and join. ???

I am guessing I am missing something very simple.

Dave

No, you wouldn't join using the wrkgadm.exe file. Are you making sure you open the database using a SHORTCUT and it references the MDW file? If you aren't then you NEED to. To create a shortcut easily I use HEADWAY SHORTCUT BUILDER (free).

 

[HiTechCoach]

I would recommend reading this:

Jack MacDonald's How I use Microsoft Access User-Level Security

 

[gemma-the-husky]

bob

does that mean that the .mdw file restrictions ARE still respected within A2010?

does deprecated just mean not recommended then?

 

[HiTechCoach]

You will find more info here:

Access JET User Level Security

 

[boblarson]

bob

does that mean that the .mdw file restrictions ARE still respected within A2010?

Yes, they are IF you are using the MDB file format and NOT the ACCDB file format.

does deprecated just mean not recommended then?

No, it means that it has been removed and no longer available. So, Access User Level Security is not available in the NEW ACCDB FILE FORMAT. It is still available in the MDB file format.

 

[HiTechCoach]

bob

does that mean that the .mdw file restrictions ARE still respected within A2010?

does deprecated just mean not recommended then?

In addition to Bob's comment, I would add that Access 2007/2010 support both JET and ACE. This allow Access 2007/2010 to with the JET (.mdb) format and the ACE (.accdb) format.

This may help:
Did you know that Access is NOT a database but a Front End?

 

[gemma-the-husky]

Yes, they are IF you are using the MDB file format and NOT the ACCDB file format.

No, it means that it has been removed and no longer available. So, Access User Level Security is not available in the NEW ACCDB FILE FORMAT. It is still available in the MDB file format.

bob - thanks for that

one last query then - if you use an accdb, does that mean that the .mdw is ignored. Is the currentuser still "admin", or is there no currentuser?

 

[HiTechCoach]

bob - thanks for that

one last query then - if you use an accdb, does that mean that the .mdw is ignored. Is the currentuser still "admin", or is there no currentuser?

ACE does not have any type of built in User Level Security. ACE does not use any work group file or prompt for a user name and password. This means that there is not really a CurrentUser property any more with an ACE (.accdb) database. I assume it is for backward comparability that the CurrentUser() does still work in 2007 with an ACE (.accdb) database.

Example in 2007 with a .accdb:

? Application.CurrentUser
Admin