Replication and FE/BE - when to do what

[cheftim]

Hi folks,


Thanks to the many of you who have helpped me get this far. I am finally ready to deploy my database! I would not have gotten this far in just a few months if it were not for your helpful advice.
One of the final stages is to place the database on the organization's server and to put FEs on each of the work stations. I've read a bit about replication and splitting of databases but I have one question I haven't found answered here...

What is the best time line for doing this?

Do I replicate the data base and then split it?
Or do I split the data base and then make replicas of the FE?

Does it matter?

Also - is replication truly needed for all data bases - I have a test copy in which I split the Access file, then just copied each front end to 2 machines and it seemed to work okay. Am I missing something that will come back and "byte" me in the keester?

Many thanks again for previous help and for your answers to this question.

t

 

[boblarson]

First, if you are using replication you will need to split the database first. Second, you probably DON'T need to use replication. You can copy the front ends to each computer. DFENTON will probably be able to chime in here about when the best time to use replication is, but my understanding is really when you either need disconnected data (i.e. on a laptop so that it can function when not attached to the network and then it can synch when the user returns to the office and hooks up to the network). I also used it once when I had a site in Sacramento, California and one in Portland, Oregon and we didn't have a fast Internet connection and so I had used replication so that we could synch our data (it didn't change all that quickly, but we did have several updates we needed propogated to each site a few times daily) and not remain connected (and they wouldn't let me use our SQL Server, which I would have preferred).

 

[cheftim]

Thanks Bob

Thank you Mr. Larson, BTW you are one of the key people I mentioned above with my thanks. There were others and I wish I could name them all, but reading your posts (both to me and to others) has been extreamly helpful.

Thank you.

t

 

[boblarson]

Thanks, I try - I've been learning this stuff for 10 years now and I keep learning new stuff by hanging out here. It's just that now I know more than I don't know. You'll get there too, I'm sure.

 

[dfenton]

Do I replicate the data base and then split it?
Or do I split the data base and then make replicas of the FE?

Split and then replicate *if* you're going to replicate the back end. If you're not, then replication plays no role here.

Also - is replication truly needed for all data bases - I have a test copy in which I split the Access file, then just copied each front end to 2 machines and it seemed to work okay. Am I missing something that will come back and "byte" me in the keester?

Replication is not suitable for front ends, as it doesn't work in the long run. It's also simply not necessary.

Replication is for *data* and only for data. If you don't have more than one location that needs to be editing the same data, then you really don't need replication at all.

There is an individual on this site who repeatedly (and wrongly) recommends using replication for updating a shared front end. The advice could not be any worse, and should be ignored.

--
David W. Fenton
David Fenton Associates
http://dfenton.com/DFA/

 

[boblarson]

Hey David - Thanks for posting on this. I made mention in my post that I hoped you would be able to chime in on it.