Database Syncroniing Prroblems

[skin76]

I have created a database---I have a copy at my office and the design master is on my laptop. The problem that I am having is now since I want to sync the two.

When I go to tools down to replication and over to snyc that options is not highligted. Not the one at my office nor on my laptop. Now I have data that I have inputted on my laptop that I need to sync to my computer at the office. Do I need to creat a replica if so how will I preserve my design master for future database stuctural changes.

 

[MoLaker]

You say you have your Design Master on your laptop and a copy on your office computer. Did you actually run Replication and create a Replica in that process? If not, then the database on your laptop is NOT a Replication Design Master and therefore, synchronization will not be available. Just a copy of your database will not synchronize.

Although not necessary, I recommend you split your database into a front-end/back-end application and only replicate the back-end. Even though you can replicate forms, etc. it's often not the best way to go. If you make updates to your front-end you can simply copy the newly updated front-end to the office location.

In making a Replica, first make a copy of your database. The main thing is to keep a copy of the table structures because Replication will add columns and hidden tables and will change autonumber fields from sequential to random. Consequently, if your database depends upon an autonumber field to have some order to it, you'd better make other plans. If you still want Replication, then run it from your laptop and create the Replica on the office system where you plan for it to reside. From then on, you can synchronze the two whenever you have interconnectivity.

Warning: Replication is not for the faint of heart. You may want to consider just passing the back-end back and forth between your laptop and office computer. If you are the only one using the database, that might be a much easier thing to control.

 

[willir]

skin76

MoLaker is correct - are you confusing the synchronizing process available on the laptop vs the replicaiton process with Access databases.

I would concur with MoLaker - using Front End / Back End is strongly recommended to separate the data and forms/reports/code modules. It simplies data updates (which happens all the time) vs form and design updates (should rarely occur.)

 

[skin76]

Where can I get more information on back-end and Front-end building, could you please reference some books that you highly approve of.

Thanks

 

[MoLaker]

There is little to discuss and less written, but there is a Wizard under Tools|Database Utilies in A2K and up. It is very briefly discussed in Help. Do a search for Split database. There are several articles and discussions about a split database. Run a Google search using the following keywords access split database. That will expose a few good links for you.

The splitting process is relatively simple. First, make a good backup of your database.

Create a blank database. Name it something that makes some sense with the name of your original (what is to be the front-end). The new blank database will be your back-end.

Open the back-end and import your tables into it. Go back and open your front-end. Delete all the tables that were imported into the back-end. Then link the front-end to the back-end tables - right click the blank space while viewing the tables list and follow Link Tables selection. The linked tables will work as though they were still within your database - as long as the locations remain the same. So, the best way in your case might be to place both front-end and back-end in the same directory.

You will access them the same way as you did before. In fact, other than making the table links, your application should not require any other changes.

Lastly, copy both the front-end and back-end to you office computer and there you are. Now if you update the back-end data at the office, you can just copy the back-end to your laptop - w/o changing any developmental work you might be doing on your front-end on the laptop. Likewise, you can copy an updated front-end to the office computer w/o messing with the data. However, if you need to make changes in table structure or add a table, you'll have to copy both front-end and back-end. Just make sure your data is synchronized before you start changing the back-end (and ALWAYS make a backup).

Now there are some other considerations, particularly in a multi-user database. That is when tables are created and deleted in the applications normal operation. Temporary tables are usually best kept in the front-end to prevent conflict with other users creating the same table name. In a single user database, this should not be a problem. However, I recommend you always develop a database with multi-user access as a possiblity.