Replication conflicts

[Dave]

This question is aimed at users of replicated databases.

We have had recently a lot of Unique Key conflicts.
Where the big keys in the tables (cant remember name)
{1234-4321-1234-4321-1234}
which should have millions , if not billions of combinations is comming up
with duplicates.

i was wondering if anyone has this problem as mush as i have.
about 5 times in 2 years (which doesnt seems alot but surely should be
virtually non-exsistant)
but once it has happened once in a replica set, thats it. it starts
happening lots
Is there something that i am doing to instigate this ?

I usually just synconise all the replicas and the copy all the tables into a
new blank database then
make another replica set out of that. Which will usually fix the situation.
untill the next time .....

any thoughts / ideas?

Dave

[Tony Toews]

"Dave" <[e-mail]> wrote:

This question is aimed at users of replicated databases.

If you don't get an answer here I'd suggest asking in the replication
newsgroup.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[David W. Fenton]

"Dave" <[e-mail]> wrote in
news:c7**********@hercules.btinternet.com:

This question is aimed at users of replicated databases.

We have had recently a lot of Unique Key conflicts.
Where the big keys in the tables (cant remember name)
{1234-4321-1234-4321-1234}
which should have millions , if not billions of combinations is
comming up with duplicates.
First off, it's simply not possible to us GUIDs as primary key in an
Access application. Access simply can't handle them.

I've never used anything but Random Autonumbers as PKs in replicated
databases, and never once had a conflict from them.
i was wondering if anyone has this problem as mush as i have.
about 5 times in 2 years (which doesnt seems alot but surely
should be virtually non-exsistant)
but once it has happened once in a replica set, thats it. it
starts happening lots
Is there something that i am doing to instigate this ?
I think using GUIDs is a fundamental error to begin with.
I usually just synconise all the replicas and the copy all the
tables into a new blank database then
make another replica set out of that. Which will usually fix the
situation. untill the next time .....

Why did you choose GUIDs? Yes, the numeric space is much larger than
with Long Integers, but on a practical basis, it's not enough to
make a difference.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc