Replication

[Guest]

Can anyone tell me where I can find the "Replication Group"?

I am having a problem with a replicated database in Access and was referred
to the Replication Group.

Thanks,
Rachel

 

[Michel Walsh]

microsoft.public.access.replication


Hoping it may help,
Vanderghast, Access MVP

 

[David W. Fenton]

Can anyone tell me where I can find the "Replication Group"?

I am having a problem with a replicated database in Access and was
referred to the Replication Group.

Do browse the archives via Google Groups -- most every topic has
already been covered.

 

[Guest]

Thank you, I will try that.

microsoft.public.access.replication


Hoping it may help,
Vanderghast, Access MVP

 

[Guest]

I tried that and can't find an answer to my problem. I suspect that I will
just need to find a different way to do what I need to do. My code works
beautifully in my master DB, but not in the replicas. But I'll keep looking.

Thank you for your response.

 

[Michel Walsh]

You can also check http://trigeminal.com/ Long time it has been updated,
but still very good info available from it, about replication with Access
(dot-mdb files).


Vanderghast, Access MVP

 

[Guest]

Thank you, Michel.

I tried the link but it said the page could not be found. Do you happen to
know if it is possible to give a replica the same rights as the master? I
have some code for a query that changes the parameters based on what the user
selects from 2 lists on a form. It works great in the master, but the
replicas get an error saying: "Run-time error 3452. You cannot make changes
to the design of this replica at this replica".

Thank your for your time.

Rachel

 

[John Spencer]

Replication is GOOD for data. It is not so good for objects such as forms,
reports, and queries.

The best way to handle this is to have a split front-end / back-end
arrangement. Link the front end to the replicated back-end (data tables).

So you have a non-replicated front end where you can change objects and a
replicated back-end where the data can be synchronized using replication.

--
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
..

 

[Michel Walsh]

You mean your ISP does not deliver the microsoft.public.access.replication
newsgroup from msnews.microsoft.com server?

Anyhow, as far as I remember, it was not wise to propagate design changes
through replication. Records, values, ok, but modifying the schema was not
without problem. I don't remember exactly to what correspond the error 3452,
but the sounds of it seems to indicate you try to do something that is not
really supported, even if you succeed in doing it by another way. Sorry, I
am not really expert in replication.


Vanderghast, Access MVP

 

[Guest]

Hi John,

The timing of your reply was perfect. I was in the middle of writing an
email to management telling them I think the problem would be solved if we
changed the database to a FE/BE format. I tried to get them to change that
before (for other reasons) and they wouldn't let me. (Resistance to change I
think.)

I will push much harder this time and tell them if they want the DB to work
as they asked, it will have to be changed.

Thank you so much.

Rachel

 

[David W. Fenton]

Replication is GOOD for data. It is not so good for objects such
as forms, reports, and queries.

Not true. Replication is *perfect* for queries, as queries are pure
Jet objects.

However, queries belong in the front end, and front ends should not
be replicated because replication does not work with
forms/reports/etc.

The best way to handle this is to have a split front-end /
back-end arrangement. Link the front end to the replicated
back-end (data tables).

This is certainly true.

So you have a non-replicated front end where you can change
objects and a replicated back-end where the data can be
synchronized using replication.

This is the correct setup.

However, I have only once in my 11 years of professional Access
programming had a requirement for changing a saved QueryDef (a
situation with a graph driven by a TOP N query, way back in Access
2). I question the need for editing the QueryDef in the first place.

 

[David W. Fenton]

You mean your ISP does not deliver the
microsoft.public.access.replication newsgroup from
msnews.microsoft.com server?

He's posting under a discussions.microsoft.com email address, which
suggest to me that he's accessing the MS newsgroups through MS's own
server, which means the replication newsgroup ought to be
accessible.

Anyhow, as far as I remember, it was not wise to propagate design
changes through replication.

Not only is it not wise, it is fatal -- it will eventually corrupt
and cause you to entirely lose the Access project.

Replication is a *Jet* technology. The objects in a front end
(forms/reports/etc.) are *Access* objects, about which Jet knows
nothing, and Jet replication doesn't handle them well in the long
term.

Records, values, ok,

Queries are pure Jet objects, too, and they can be replicated
without issue. But queries belong in the front end, so it's unlikely
you'll have very many replicated queries.

but modifying the schema was not
without problem. I don't remember exactly to what correspond the
error 3452, but the sounds of it seems to indicate you try to do
something that is not really supported, even if you succeed in
doing it by another way. Sorry, I am not really expert in
replication.

It's simply an indication that he can't make design changes at a
replica. But he shouldn't be *using* a replica in the first place.

 

[Guest]

Thank you all for your input. It was very helpful and much appreciated.

Rachel