Split Database with Synchronization
From: Kevin McBrearty (KevinMcBrearty_at_discussions.microsoft.com)
Date: 06/28/04
- Next message: Tim Ferguson: "Re: Tracking items sold under a sale or return scenario."
- Previous message: Kevin3NF: "Re: Help - Convert Access flat file to normalized tables"
- Next in thread: Joan Wild: "Re: Split Database with Synchronization"
- Reply: Joan Wild: "Re: Split Database with Synchronization"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 28 Jun 2004 13:42:01 -0700
I am currently designing a database that will be used on a LAN and a number of remote laptops that may or may not have access to the internet.
I would like to be able to have a split database so that I can modify the front end without have to worry about bringing the data over to a new database. I already know how to accomplish this, I am just mentioning it to see if anyone can forsee any problems that I may have.
Now to get into Synchronization, I know how to accomplish this in a database that is not split by creating a replica. I don't know that I entirely like the way that it works but I can get it to work. The problem I am running into is when I split the database into two parts, and being able to syncronize the backend while using the frontend.
My other concern, Is this the best way to accomplish syncronizing the database with the situation that I have. I know I often design a database one way, to find out later that it would have worked better had I done it a different way. I am trying to avoid that realization on this database project.
Any help you could provide would be much appreciated. Thank you in advance for you time.
- Next message: Tim Ferguson: "Re: Tracking items sold under a sale or return scenario."
- Previous message: Kevin3NF: "Re: Help - Convert Access flat file to normalized tables"
- Next in thread: Joan Wild: "Re: Split Database with Synchronization"
- Reply: Joan Wild: "Re: Split Database with Synchronization"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|