"st***@acid.ro" <st***@acid.ro> wrote in
news:11**********************@g43g2000cwa.googlegr oups.com:
I have an access database replicated over a network. Recently and
more often, after I fill one record into the database, and then
try to replicate it, I get this message "scaling of decimal
values resulted in data truncation".
I'm not sure. Have you compacted the problematic replica?
I think there is nothing wrong with my database, because the same
record, introduced on another computer gives me no errors. And
after replacing the faulty replica on that computer, everything
works fine. (for a while)
And I have another question... when I copy a replica (or even the
design master) on another computer, it's the same thing whith
creating replicas from the design master?
Copying replicas ONE TIME is OK. That is, if you have a computer
and
it has no replica on it, you can copy a replica there, and it will
work fine.
However, that replica can *not* then be copied back to some other
location and synched withthe replica set. Once a replica is in its
location it has to stay there -- any copying operation always
creates a new ReplicaID, even if the file is the same (it's the
different location that causes Jet to generate a new RreplicaID).
Replicas created by copying are *not* the same as replicas created
from the Design Master, unless you're actually copying the design
master. THe difference is in the replica priority, which controls
how conflicts are resolved.
If you're copying just to create a new replica, that's fine.
If you're copying over top of an existing replica, then that's
very,
very bad. -- search the microsoft.public.access.replication
newsgroup for the phrase "dead replicas."
--
David W. Fenton
http://www.bway.net/~dfenton
dfenton at bway dot net
http://www.bway.net/~dfassoc