Ok, I know that the user-level security has been removed from Access 2007 but
I wanted to share something I found and see if anyone else has experienced
this or what anyones thoughts were.

We upgraded to Access 2007 and saved our existing 2003 database to 2007. I
then realized that we wanted to hang onto the User-level security for a short
time so I resaved the database as a 2003 .mdb database. I also left the 2007
version out there to use for testing. We put the database on a different
server (for other reasons) so when I went in I had to set the user-level
security up again. I admittedly don't know a ton about how the user-level
security works so I may have not done it how it was supposed to be done.
Anyway, our 2003 database seemed to be working fine and doing what we wanted
it to do. I went into the 2007 database to do some testing and noticed that
when I log in it asked me for a UserName. It then would correctly do the
=CurrentUser() function that it was calling on one of my forms. I am 100%
positive that I pulled up the 2007 database - I even went to the Database
utilities menu and the User and Permissions button wasn't there.

I guess I am assuming that somehow the 2007 database is utilitizing the
SYSTEM.MDW file and that the user permissions was set by the 2003 database
but since they use the same file that is why it is showing up. I tested it a
bit on my local machine and that seemed to be the case. I can't imagine this
was intended however. Anyone have any thoughts?

Arica

"QuadSquad" wrote:

> Ok, I know that the user-level security has been removed from Access 2007 but
> I wanted to share something I found and see if anyone else has experienced
> this or what anyones thoughts were.
>
> We upgraded to Access 2007 and saved our existing 2003 database to 2007. I
> then realized that we wanted to hang onto the User-level security for a short
> time so I resaved the database as a 2003 .mdb database. I also left the 2007
> version out there to use for testing. We put the database on a different
> server (for other reasons) so when I went in I had to set the user-level
> security up again. I admittedly don't know a ton about how the user-level
> security works so I may have not done it how it was supposed to be done.
> Anyway, our 2003 database seemed to be working fine and doing what we wanted
> it to do. I went into the 2007 database to do some testing and noticed that
> when I log in it asked me for a UserName. It then would correctly do the
> =CurrentUser() function that it was calling on one of my forms. I am 100%
> positive that I pulled up the 2007 database - I even went to the Database
> utilities menu and the User and Permissions button wasn't there.
>
> I guess I am assuming that somehow the 2007 database is utilitizing the
> SYSTEM.MDW file and that the user permissions was set by the 2003 database
> but since they use the same file that is why it is showing up. I tested it a
> bit on my local machine and that seemed to be the case. I can't imagine this
> was intended however. Anyone have any thoughts?
>
> Arica

When you say "System.mdw" is this the file that is in your Windows/Settings
folder or did you create a new Workgroup file, name it System.mdw and save it
in the database folder?

If it is the Windows .mdw file, your problem is that your security settings
are saved onto your computer, not specifically to the database. By doing
this, all of your Access databases will require a logon, even though you have
done nothing to "secure" them.

When using Group or User level security, you should create an individual
workgroup file for each database. This file is saved in the folder that
contains the database. In this way there is no "crossover" of security
settings from one database to another.