I am fairly sure that the only DB that needs to be replicated would be the back-end, since it's the data that replication deals with. The front end might have "utility" tables for basic lists that don't change, but nothing that is stored for the client.
Tobi -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of wartheit Sent: Thursday, January 05, 2006 9:36 AM To: [email protected] Subject: [AccessDevelopers] Re: Need help on replicating mdb Hi Jeanie, I'm glad you found my post helpful. I'm no guru, nor do I make posts often, but I like to help when I can. Unfortunately, I have never tried replicating with a split db, so I don't know how that would work. I've never tried syncronizing over the Internet either, only our office LAN. That could prose its own set of problems (dropped packets or connections, etc.). I'm curious to find out if any readers have tried this before and how Access handles it. Sorry I don't have any experience to share with this part of your project. Maybe the next question ... Paul --- In [email protected], "Jeanie S" <[EMAIL PROTECTED]> wrote: > > That's great information, Paul. Thank you. I knew that Access added > fields, I just did not know about the timing or the randomness. > > My related question then is this. I have the front end of my project > in one mdb and the data tables in another. Can I replicate just the > data tables and keep the driver program the same? It's the data I'm > concerned about merging but I don't want to have to have the master > program reside in England with the data as I am in Florida. I'd like > to keep the master program here (hopefully with just copies, not > replications of it on the team laptops and at the office in Cowes). > > Thoughts on the two mdb files? > > -- Jeanie > > --- In [email protected], "wartheit" <[EMAIL PROTECTED]> wrote: > > Tobi's right. Access actually adds a number of hidden/system fields > to > each table and converts sequential autonumber fields to random number > (I think it is in Long Number format). I've used replicated databases > for years and have only had one problem. The databases need to be > syncronized regularly otherwise the replica becomes "aged" and Access > won't sync with it any more. I think the limit is about 1 month > (Anybody able to confirm the time limit for me?). > > One other thing about relication is that you can only make design > changes to the Design Master (the original database). This helps avoid > users changing things on you. Also, should the Design Master become > corrupt, you can elevate one of the replicas to become the new Design > Master, almost a "built-in backup". > > Hope it works well for you. > > Paul > > --- In [email protected], "Jeanie S" <[EMAIL PROTECTED]> > wrote: > > Thanks for that info, Tobi. That eases my mind a little bit to know > that the autonumbers will be random instead of sequential. Now I > suppose it's time to test it out. > > Unless someone else has a reference for replicating that I can look > at before I jump in. > > -- Jeanie > > --- In [email protected], "Tobi Hoffman" > [EMAIL PROTECTED]> wrote: > > When you go to a replicated database system, the Autonumber keys > become random numbers rather than sequential, and with the number of > digits used, it would be highly unlikely to have duplicate keys in > the different replica databases. That being said, I have looked at, > but have not yet used replicated databases, and would still prefer > to > use other means to pull in data to a master database. Anybody else > out there with more experience using replication?! > > Tobi > Please zip all files prior to uploading to Files section. Yahoo! Groups Links Please zip all files prior to uploading to Files section. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AccessDevelopers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
