If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.

2003 to 2007

My understanding is that if I upgrade a 2003 format .mdb to 2007 all security
settings will be gone. Can someone elaborate on just what that means? I
presume no login, no workgroup. How about database password? I am presuming
therefore that security is dealt with through the GUI - e.g. forms would
determine that the info in a table would be read only or the GUI would not
include links to certain features. But let's say that the person just shuts
down the switchboard form and leaps into tables. and gets what they want that
way. I need a little more info. Does it mean that a front-end/back-end would
be required? Are there any options that would give me a way of making the
database secure in the way that previous editions of Access did? Now I know
someone is going to leap in and say that it wasn't "really" secure before,
but if you really followed the process and removed the Admin from the Admins
group and made someone else Admin and used the logins/permission & passwords
plus the database password, and then "secured" it, I think you really were
pretty well covered. But that's just my opinion... All ideas most welcome.

security in access 2007 can be implemented on several levels:
* encrypt the file with a password
* make an accde file :mainly protects any code and form/report design, but
allows the users to enter the tables
* make a runtime executable using the developers extensions. These can be
downloaded free on http://msdn.microsoft.com/en-us/office/bb229700.aspx
Beware that using the runtime the user looses a lot of build-in features like
search functions, so the developer has to program these in her/his
application.

success
NG

sweeneysmsm wrote:
My understanding is that if I upgrade a 2003 format .mdb to 2007 all security
settings will be gone. Can someone elaborate on just what that means? I
presume no login, no workgroup. How about database password? I am presuming
therefore that security is dealt with through the GUI - e.g. forms would
determine that the info in a table would be read only or the GUI would not
include links to certain features. But let's say that the person just shuts
down the switchboard form and leaps into tables. and gets what they want that
way. I need a little more info. Does it mean that a front-end/back-end would
be required? Are there any options that would give me a way of making the
database secure in the way that previous editions of Access did? Now I know
someone is going to leap in and say that it wasn't "really" secure before,
but if you really followed the process and removed the Admin from the Admins
group and made someone else Admin and used the logins/permission & passwords
plus the database password, and then "secured" it, I think you really were
pretty well covered. But that's just my opinion... All ideas most welcome.

Thanks for your so prompt reply. I guess it seems that Access 2007 security
is "across the board" but does not allow for the wonderful fine-tuning that
previous versions permitted - the ability to modify users' powers according
to their login. For me it was so very helpful to give someone read only power
or to lock them out of different segments.

I am still looking for the answer to what happens if someone has a secured
2003 .mdb with its own .mdw but then upgrades to 2007 format. Exactly what
changes. All passwords, permissions discarded? General open entry?

If I went the way of the accde it sounds as if a new file is created where
the user does not have access to code. Is it like a front-end which is linked
back to the tables in the original database? From my perspective, I am just
wondering how subsequent changes to the design would be achieved without loss
of data.

Any further thoughts?

Mary

"NoellaG via AccessMonster.com" wrote:
Hi there,

security in access 2007 can be implemented on several levels:
* encrypt the file with a password
* make an accde file :mainly protects any code and form/report design, but
allows the users to enter the tables
* make a runtime executable using the developers extensions. These can be
downloaded free on http://msdn.microsoft.com/en-us/office/bb229700.aspx
Beware that using the runtime the user looses a lot of build-in features like
search functions, so the developer has to program these in her/his
application.

success
NG

sweeneysmsm wrote:
My understanding is that if I upgrade a 2003 format .mdb to 2007 all security
settings will be gone. Can someone elaborate on just what that means? I
presume no login, no workgroup. How about database password? I am presuming
therefore that security is dealt with through the GUI - e.g. forms would
determine that the info in a table would be read only or the GUI would not
include links to certain features. But let's say that the person just shuts
down the switchboard form and leaps into tables. and gets what they want that
way. I need a little more info. Does it mean that a front-end/back-end would
be required? Are there any options that would give me a way of making the
database secure in the way that previous editions of Access did? Now I know
someone is going to leap in and say that it wasn't "really" secure before,
but if you really followed the process and removed the Admin from the Admins
group and made someone else Admin and used the logins/permission & passwords
plus the database password, and then "secured" it, I think you really were
pretty well covered. But that's just my opinion... All ideas most welcome.

On Fri, 28 May 2010 13:47:01 -0700, sweeneysmsm
wrote:
I am still looking for the answer to what happens if someone has a secured
2003 .mdb with its own .mdw but then upgrades to 2007 format. Exactly what
changes. All passwords, permissions discarded? General open entry?

Nothing happens - security still works, *provided* you use the .mdb format.
It's only when you convert to .accdb or .accde format that security goes away.
It doesn't even look at the .mdw file, there is no logon prompt, and none of
the object security specifications are honored.

You can (at least in 2007 or 2010) still use a secured .mdb or .mde file, with
an associated .mdw, and security will still continue to be honored.
--

"John W. Vinson" wrote:
On Fri, 28 May 2010 13:47:01 -0700, sweeneysmsm
wrote:
I am still looking for the answer to what happens if someone has a secured
2003 .mdb with its own .mdw but then upgrades to 2007 format. Exactly what
changes. All passwords, permissions discarded? General open entry?

Nothing happens - security still works, *provided* you use the .mdb format.
It's only when you convert to .accdb or .accde format that security goes away.
It doesn't even look at the .mdw file, there is no logon prompt, and none of
the object security specifications are honored.

You can (at least in 2007 or 2010) still use a secured .mdb or .mde file, with
an associated .mdw, and security will still continue to be honored.
--