|Date Added: March 11, 2012 12:37:53 PM|
Always up to date so the information should be a database. This only works if the data is constantly updated and if the database is always available.
Database maintenance for a single user system, the responsibility therefore in your own hands, because you only have to worry about updating. In a company with a larger network or with employees who are not always available locally, there are there other problems. In many applications, namely the joint is possible to access a database not over a network.
For example, access by field staff
Sales representatives capture orders on their laptops and want it to use current data item and discount scales. How can you ensure that you expand the database in both your company and the sales force to enable the capture of data?
(See also my tip on this: ACCESS_aktuell - Brand new tip for your access.) This further helps the database replication, because after appropriate preparation, you can create multiple copies of a database that can then later merge automatically.
Who needs replicated databases?
As in our example, it may happen that not all departments at the local corporate network is connected or that the field staff working on the go with laptops that are at this time of course, not connected with the company.
Nevertheless, the information from the company database somehow be handy. The simplest solution would be transmitted to the central database at certain time intervals to the remote units or to the field worker. This could be done via CD-ROM, memory stick or via e-mail. Laptop users could log in, even temporarily on site in the network.
This method has one catch, however, because the transfer is made in only one direction.
There will be transferred out only the latest data from the Central Company. Changes on the part of non-affiliated sites ever found in this scenario, no space, so the process lends itself only when the central databases are relatively static (eg: general mailing lists and telephone directories).
Often the business data must be not only at headquarters, but also elsewhere edited. Representatives accept such orders; attract new customers, branches, etc. At the same time update the inventory before the panel may address changes in the stock or similar to prices.
This confluence of all this information again at the end in a large central database, you need a tool that compares the edits.