 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / October 2006allowing multi user access 2003 database
Hi I have recently designed a simple access 2003 database which i would like other people to have access to and also for them to make changes. I was just wondering what security requirements and data integrity issues i need to cover before allowing multi user access. How do i avoid any replication errors? There are no queries being run in this database, just tables and forms. It is simply a storage place for lots of data which i need to share with alot of people. Any additional hints and tips on setting up and maintaining the database would be appreciated. thanks Matt Access is multi-user-enabled by design, out-of-the box, but there are a few things to consider to avoid performance difficulties and occasional corruption. My first advice always is: split the database into front-end (queries, forms, reports, macros, and modules, and occasionally a few rarely-changing lookup tables) and back-end (tables, relationships, and data). Microsoft has thoughtfully provided a "database splitter"... in Access 2002, that is found on the Menu, Tools | Database Utilities | Database Splitter. You can use the Linked Tables Manager, or your own code, to link the tables. All the users get their own copy of the front-end and cocurrently use the same copy of the back end. "Replication" is a very specific term in Access -- a different situation in which each user gets a copy of the back-end and they are "synchronized." Unless you have compelling need (e.g., sales people carrying laptops who come in to the office just every few days, etc.), you don't want to go there. Conflicting updates and "collisions" are generally not a problem, even with the lowest level of "locking." A very, very good source of tips and hints on multiuser, especially avoiding performance problems and database corruption is MVP Tony Toews' site, http://www.granite.ab.ca/accsmstr.htm. Good luck with your project. Larry Linson > Hi > [quoted text clipped - 10 lines] > > Matt Dear Matthew: You are in luck; Access is multi-user right out of the box! In order to allow for multiple users, you will need to "split" your database, and put an MDB file with the tables in a shared folder (with full permissions for all users) on the server, and put an MDB file with the forms, reports and queries on each workstation. The tables file is usually called the "Back End" and the file on the workstation is usually called the "Front End". All of the front end files will link to the single back end tables. For much, much more info, check out the links here: http://home.bendbroadband.com/conradsystems/accessjunkie/splitting.html As for security, that is another issue - and a big one! Security in Access is not easy, so if you want to implement it, be prepared for a steep learning curve. Resources and links here: http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html#Security HTH Fred Boer > Hi > [quoted text clipped - 10 lines] > > Matt thanks for your help. I have now split the database and understand the principle behind it however how do i stop front end users changing the data in the forms because at the moment when i change something in the front end database in form view when i close the form it updates the back end database i dont want that. apprecitae your help. > Dear Matthew: > [quoted text clipped - 33 lines] >> >> Matt Hello: So, you want the users to view, but not edit the data? Try setting the following form properties to "No": "Allow Edits"; "Allow Deletions"; "Allow Additions". HTH Fred Boer > thanks for your help. I have now split the database and understand the > principle behind it however how do i stop front end users changing the data [quoted text clipped - 19 lines] > > is not easy, so if you want to implement it, be prepared for a steep > > learning curve. Resources and links here: http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html#Security > > HTH > > Fred Boer [quoted text clipped - 13 lines] > >> > >> Matt excellent exactly what i want.. thanks again. > Hello: > [quoted text clipped - 61 lines] >> >> >> >> Matt Dear Matthew: You are welcome! Cheers! Fred > excellent exactly what i want.. thanks again. > > Hello: [quoted text clipped - 31 lines] > >> > > >> > For much, much more info, check out the links here: http://home.bendbroadband.com/conradsystems/accessjunkie/splitting.html > >> > As for security, that is another issue - and a big one! Security in > > Access > >> > is not easy, so if you want to implement it, be prepared for a steep > >> > learning curve. Resources and links here: http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html#Security > >> > HTH > >> > Fred Boer [quoted text clipped - 17 lines] > >> >> > >> >> Matt |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.