 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Replication / May 2008how safe is replication for the uninitiated?
A customer of mine would very much appreciate the option of replication, but I do not believe that he is able to overcome eventual problems himself, when they occur. I do not have experience with replication and I doubt if I can assist the customer in case of trouble, because I live in an other country. Does this mean that replication is not an option? How safe can I make it. Would TSI Synchronizer make things safer? Thanks for your ideas Michiel First question - is replication really necessary? David Fenton, who often writes here, is an expert on replication and recommends that you should consider using Terminal Server as a better alternative. The primary situation where replication is necessary is to support mobile users who must enter data into the database and who are disconnected from the network. Does that apply to your situation? Replication can be fraught with difficulty. If you do things incorrectly, you can corrupt your database -- which I suppose is "unsafe". Here's a good resource: http://www.dfenton.com/DFA/Replication/index.php?title=Main_Page >A customer of mine would very much appreciate the option of replication, but >I do not believe that he is able to overcome eventual problems himself, when [quoted text clipped - 9 lines] > >Michiel -- jackmacMACdonald@telusTELUS.net remove uppercase letters for true email http://www.geocities.com/jacksonmacd/ for info on MS Access security Yes, it is a situation where there's an office and a salesman on the road. With one salesman we can manage. But the option of expansion, of course, is attractive. On one location they use PcAnywhere to reach the server in the office. I believe, from what I read, it serves a bit like Terminal Server. But only for one. I wonder how many actually use replication and how many of them have sometimes to turn to this newsgroup (or others, or their IT dept) because of problems. How many don't have to? In a repair department you easily could get the impression that a product is plain rubbish, just because you see only the problematic ones. Indeed Mr Fenton is very clear and informative, so the least thing one can do is following up his 'Best practises'. Still, problems can occur, so I at least should offer a kind of backup. Is it in theory possible that in case of trouble, an expert addresses a 'messed-up' replicated backend through remote access? thanks for your thoughts and input! Michiel > First question - is replication really necessary? David Fenton, who > often writes here, is an expert on replication and recommends that you [quoted text clipped - 30 lines] > remove uppercase letters for true email > http://www.geocities.com/jacksonmacd/ for info on MS Access security >Yes, it is a situation where there's an office and a salesman on the road. >With one salesman we can manage. [quoted text clipped - 8 lines] >their IT dept) because of problems. >How many don't have to? Impossible for me to answer that question. >In a repair department you easily could get the impression that a product is >plain rubbish, just because you see only the problematic ones. > >Indeed Mr Fenton is very clear and informative, so the least thing one can >do is following up his 'Best practises'. >Still, problems can occur, so I at least should offer a kind of backup. It's been my experience that maintenance is required on occasion, and the maintenance person must have a deep understanding of how replication works. Also very important is knowledge about how to set up the process in the first place. It's very easy to (incorrectly!) assume what *might* work, only to find it fail after a period of time. If your salesman returns to the office periodically and is able to connect to the LAN to synchronize the database, setup will be greatly simplified. On the other hand, if he needs to connect remotely, then you will need to set up Indirect Synchronization which introduces another layer of complexity. >Is it in theory possible that in case of trouble, an expert addresses a >'messed-up' replicated backend through remote access? Yes - you can log in via remote access to perform maintenance. I use PCAnyware, VNC, LogMeIn, and Terminal Server depending on the location. All you need is access to the machine via some method. BTW - although David wrote most of the Wiki articles, I contributed the Best Practices, so I appreciate the positive feedback. >thanks for your thoughts and input! > [quoted text clipped - 34 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 fortunately, he comes to the office almost every day. so, that is at least something. It is reassuring to read, that remote access is an option for replication support. For the moment I will try to acquire a 'deeper' understanding of replication. Thanks for your help. Here and in the Wiki Michiel >>Yes, it is a situation where there's an office and a salesman on the road. >>With one salesman we can manage. [quoted text clipped - 86 lines] > remove uppercase letters for true email > http://www.geocities.com/jacksonmacd/ for info on MS Access security Since he comes to the office frequently, you have a big advantage. He only needs to plug his notebook computer into the LAN, and synchronize directly with the version stored on the LAN. That can be done either via the built-in user interface from the backend database, or you can write a bit of code to synchronize directly from the frontend. It's up to you... depends on the user's sophistication and your ability to write VBA code. Either way is fairly simple. >fortunately, he comes to the office almost every day. >so, that is at least something. [quoted text clipped - 6 lines] > >Michiel -- jackmacMACdonald@telusTELUS.net remove uppercase letters for true email http://www.geocities.com/jacksonmacd/ for info on MS Access security > Indeed Mr Fenton is very clear and informative, so the least thing > one can do is following up his 'Best practises'. > Still, problems can occur, so I at least should offer a kind of > backup. Truth be told, the "Best Practices" page was not written by me, but by the person you've been corresponding with. > Is it in theory possible that in case of trouble, an expert > addresses a 'messed-up' replicated backend through remote access? I do most of my replicated work remotely, in fact, in Florida, Texas, upstate NY and other places.  SignatureDavid W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
|
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.