Splitting a replica set   

I am currently runnning a mdb where the design master is held on a laptop. 
One replica runs from the server at one location and another from the server 
at a second location.  Location 1 has the problem where every so often the 
replica corrupts - recommendation is that I split the database, however as I 
have not done this before, I'm not sure of all the ins and outs.  Ideally 
the whole database needs to be held on the laptop and therefore portable. 
Locations 1 and 2 both need access at all times. My questions are:
1) Can a split database be replicated and does that include the front end as 
well as the back end
2) Can the back end be used over VPN or does it slow down drastically if so 
syncronising is what I do now so not a major issue
3) How complicated is it to make design changes to a split database
Any help would be appreciated
Thanks in advance

Charlie

date: Tue, 21 Mar 2006 18:54:17 GMT   author:   Charlie

Re: Splitting a replica set   

"Charlie"  wrote in
news:tZXTf.205513$Q22.10779@fe1.news.blueyonder.co.uk: 

> I am currently runnning a mdb where the design master is held on a
> laptop. One replica runs from the server at one location and
> another from the server at a second location.  Location 1 has the
> problem where every so often the replica corrupts - recommendation
> is that I split the database, however as I have not done this
> before, I'm not sure of all the ins and outs.  Ideally the whole
> database needs to be held on the laptop and therefore portable. 
> Locations 1 and 2 both need access at all times. My questions are:
> 1) Can a split database be replicated and does that include the
> front end as well as the back end

Both front end and back and *can* be replicated, but it will only
ever work with the back end, the data tables, because replication
was designed for Jet objects, not for Access objects. Tables and
queries are pure Jet objects, while forms, reports, etc. are Access
(i.e., objects whose definitions are stored in Jet data tables). 

Front end changes can be propagated by simply copying the new front
end over top of the old. Distribution can be through email or any
number of methods. 

But replication is not one of them that works.

> 2) Can the back end be used over VPN or does it slow down
> drastically if so syncronising is what I do now so not a major
> issue 

Unless you've got 10Mbps of bandwidth or more on your VPN, not you
can't connect to the back end directly. It will be much too slow to
be usable, no matter how you design your application. 

> 3) How complicated is it to make design changes to a split
> database Any help would be appreciated

I don't understand the question. I've never made any changes to
anything *but* a split database, as that's the only kind I've ever
created in my 10 years as a professional Access developer. 

-- 
David W. Fenton                  http://www.dfenton.com/ 
usenet at dfenton dot com    http://www.dfenton.com/DFA/

date: Tue, 21 Mar 2006 14:57:48 -0600   author:   David W. Fenton lid