|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
2007 access to a 2003 databaseHi
I have a database in 2003 that has user-level security. This database is located on a server and 7 people have access to it. One of these people has Access 2007. When they try and open the database they are told that they do not have "Open/Run permission" for the form that is opened with the Startup. Also, they are not asked to give a username or password when Access is opened. Once I gave them permission in the 2003 version of the database to open the form, that appears but nothing else works. Anybody have any ideas how this database can be opened and used in 2007 but remain a 2003 file??? Thanks The Access 2007 user isn't joined to the secure workgroup. The fact that
he/she is opening it anyway means it's not fully secured. 1 - Read and study the security faq and then secure the db. http://support.microsoft.com/?id=207793 2 - Split the db into a front end and back end. Back end has tables and relationships only and is placed on the server. Front end has everything else plus links to the back end tables. A copy of the front end is on each user's desktop. All multiuser Access dbs should be set up this way to avoid corruption and the problems with sharing the db file. How does this sound? Your Access 2007 user could have an Access 2007 version of the front end on his desktop and not interfere with the Access 2003 users by reseting the library paths. 3 - Make a shortcut. (All one line) "path to msaccess.exe" "path to db.mdb" /wrkgrp "path to db.mdw" All users should be joined permanently to the default system.mdw workroup file and use shortcuts to open secure dbs. How does this sound? They won't be prompted for user name and password unless they're opening a secure db. Chris BCiel wrote: >I have a database in 2003 that has user-level security. This database is >located on a server and 7 people have access to it. One of these people has >Access 2007. When they try and open the database they are told that they do >not have "Open/Run permission" for the form that is opened with the Startup. >Also, they are not asked to give a username or password when Access is opened. > >Once I gave them permission in the 2003 version of the database to open the >form, that appears but nothing else works. > >Anybody have any ideas how this database can be opened and used in 2007 but >remain a 2003 file??? First the security faq that you recommended is for Access 2000 and my files
are 2003. I would rather not split the database into front end and back end if at all possible. The reason that the database is secured was to lessen the possibility of problems and corruption while sharing the db file. I really just need to get the 2007 user able to open and run the reports that are located in this database. That Access opens logged in as Admin automatically but is not given the same permissions as the 2003 Admin. Thanks but I still am looking for help. Show quoteHide quote "Chris O'C via AccessMonster.com" wrote: > The Access 2007 user isn't joined to the secure workgroup. The fact that > he/she is opening it anyway means it's not fully secured. > > 1 - Read and study the security faq and then secure the db. > > http://support.microsoft.com/?id=207793 > > 2 - Split the db into a front end and back end. Back end has tables and > relationships only and is placed on the server. Front end has everything > else plus links to the back end tables. A copy of the front end is on each > user's desktop. All multiuser Access dbs should be set up this way to avoid > corruption and the problems with sharing the db file. > > How does this sound? Your Access 2007 user could have an Access 2007 version > of the front end on his desktop and not interfere with the Access 2003 users > by reseting the library paths. > > 3 - Make a shortcut. (All one line) > > "path to msaccess.exe" "path to db.mdb" /wrkgrp "path to db.mdw" > > All users should be joined permanently to the default system.mdw workroup > file and use shortcuts to open secure dbs. How does this sound? They won't > be prompted for user name and password unless they're opening a secure db. > > Chris > > > BCiel wrote: > > >I have a database in 2003 that has user-level security. This database is > >located on a server and 7 people have access to it. One of these people has > >Access 2007. When they try and open the database they are told that they do > >not have "Open/Run permission" for the form that is opened with the Startup. > >Also, they are not asked to give a username or password when Access is opened. > > > >Once I gave them permission in the 2003 version of the database to open the > >form, that appears but nothing else works. > > > >Anybody have any ideas how this database can be opened and used in 2007 but > >remain a 2003 file??? > > -- > Message posted via http://www.accessmonster.com > > BCiel wrote:
> First the security faq that you recommended is for Access 2000 and my files Doesn't matter. It's still applicable to 2003.> are 2003. > I would rather not split the database into front end and back end if at all Securing it does nothing to lessen the possibility of corruption. Not > possible. The reason that the database is secured was to lessen the > possibility of problems and corruption while sharing the db file. splitting however, increases the probability of corruption (even more so with differing versions of Access). > I really just need to get the 2007 user able to open and run the reports The 2007 user can use the 2003 database. Just give them a desktop > that are located in this database. That Access opens logged in as Admin > automatically but is not given the same permissions as the 2003 Admin. shortcut with the following in the target. "path to 2007 msaccess.exe" "path to 2003 mdb" /wrkgrp "path to secure.mdw" If you insist on finding out for yourself the perils of running an unsplit mdb with multiple users/versions, please remember to backup often. Good luck. Joan Wild MS Access MVP Joan Wild <jwild@nospamtyenet.com> wrote in
news:OjdNB$$dJHA.1268@TK2MSFTNGP04.phx.gbl: The reason it's still applicable is because Access 2000-2007 all use> BCiel wrote: >> First the security faq that you recommended is for Access 2000 >> and my files are 2003. > > Doesn't matter. It's still applicable to 2003. Jet 4 for MDBs, and ULS is a Jet 4 (not an Access) feature. You need to follow what Joan said and make a desktop shortcut like the
example she gave you. It will work. I just upgraded and have some users using access 2007 and some using 2003. The 2007 users need the shortcut because of the user level security file. Access 2007 does not use that anymore. Show quoteHide quote "David W. Fenton" wrote: > Joan Wild <jwild@nospamtyenet.com> wrote in > news:OjdNB$$dJHA.1268@TK2MSFTNGP04.phx.gbl: > > > BCiel wrote: > >> First the security faq that you recommended is for Access 2000 > >> and my files are 2003. > > > > Doesn't matter. It's still applicable to 2003. > > The reason it's still applicable is because Access 2000-2007 all use > Jet 4 for MDBs, and ULS is a Jet 4 (not an Access) feature. > > -- > David W. Fenton http://www.dfenton.com/ > usenet at dfenton dot com http://www.dfenton.com/DFA/ >
Other interesting topics
BE/ FE Question
vba opendatabase readonly Linking to a password protected BE from FE Security Problem When Linking Tables record level lock access 2002 can't disable shift key with faq_DisableShiftKeyBypass function Secure part of a db? recordset not updatabale User Level Security on Replicated Other methods for preventing "not have exclusive access at this time" message? |
|||||||||||||||||||||||