 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / December 2004Design Question
Hello, I have just started my first access project and need some advice. The setup would be 5-10 people working on a lan and some external people with laptops accessing the database. My fist design-choice would be to split the database into a FE/BE database with the frontend installed on each users computer. Now several question arise to me : 1.) How to implement the database on the laptops. also as a FE/BE database, or just a plain one? 2.) How do I keep the data consistent between the BE-data on the LAN and the data on the laptops? I have read about Replication, but are there any other possibilities that work? regards, alex pandit Hi Alex, 1. anyway it is better to implement splitted database 2. Depends on what kind of tasks people should perform on laptops. if they need to have all kind of update possibilities - then probably replication is only option. but it required a skilled person to be on support  SignatureAlex Dybenko (MVP) http://Alex.Dybenko.com http://www.PointLtd.com > Hello, > [quoted text clipped - 20 lines] > > regards, alex pandit > Hi Alex, > 1. anyway it is better to implement splitted database > 2. Depends on what kind of tasks people should perform on laptops. if > they need to have all kind of update possibilities - then probably > replication is only option. but it required a skilled person to be on > support The project is a customer-managment database where internal and external (laptop) workers add and update customer-date. So as you say replication is the way to go. Your last sentence scares me off a bit. What are the major problems that can arise with replication ? I guess it could have something to do with identical keys in the tables. thnx, alex Well, from my experience of using replication you should aware 3 things: - should be implemented a good procedure to resolve conflicts - you should care about expired replicas, should be implemented strong synchronozation schedule - should be a procedure what user should do in case of data corruption. as you see - nothing special, but it is important to have somebody who can continiously look at the process and know what to do SignatureAlex Dybenko (MVP) http://Alex.Dybenko.com http://www.PointLtd.com >> Hi Alex, >> 1. anyway it is better to implement splitted database [quoted text clipped - 11 lines] > > thnx, alex In addition to these points, you should also consider how the laptops will be synchronized. Will they be physically connected to the LAN during synchronization? Otherwise, you must consider using Indirect or Internet synchronization, which adds a level of complexity. You may *not* email replicas or send them via CD, etc. >Well, from my experience of using replication you should aware 3 things: >- should be implemented a good procedure to resolve conflicts [quoted text clipped - 4 lines] >as you see - nothing special, but it is important to have somebody who can >continiously look at the process and know what to do ********************** jackmacMACdonald@telusTELUS.net remove uppercase letters for true email http://www.geocities.com/jacksonmacd/ for info on MS Access security > In addition to these points, you should also consider how the laptops > will be synchronized. Will they be physically connected to the LAN > during synchronization? Otherwise, you must consider using Indirect or > Internet synchronization, which adds a level of complexity. You may > *not* email replicas or send them via CD, etc. Hi Jack, the laptops will be physically connected to the LAN when synchronyzing. Are there any "best practices" or code how to avoid/handle conflicts? thnx alex >> Well, from my experience of using replication you should aware 3 >> things: [quoted text clipped - 11 lines] > remove uppercase letters for true email > http://www.geocities.com/jacksonmacd/ for info on MS Access security The best source of info about replication is www.trigeminal.com also see http://www.access-experts.com/default.aspx?selection=TutorialReplication&sm=18 Best practices for avoiding conflicts -- avoid having two people edit the same record. Depending on your database content, that may be a natural occurrence, or you may need to create a policy for your users. >> In addition to these points, you should also consider how the laptops >> will be synchronized. Will they be physically connected to the LAN [quoted text clipped - 24 lines] >> remove uppercase letters for true email >> http://www.geocities.com/jacksonmacd/ for info on MS Access security ********************** jackmacMACdonald@telusTELUS.net remove uppercase letters for true email http://www.geocities.com/jacksonmacd/ for info on MS Access security > Well, from my experience of using replication you should aware 3 > things: [quoted text clipped - 6 lines] > as you see - nothing special, but it is important to have somebody > who can continiously look at the process and know what to do Thank you for your advice. Do you know any resources where i can read more about the points you mentioned above? thnx, alex |
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.