Tables disappear after syncrhonization

[akphidelt]

Hello gurus, Im having a little problem that I can not fix on my own.
Actually I can't even get access to the database but a coworker of mine
called me about a database I had built them and they are using replications
and synchronizations to make it work.

Apparently they did something where when after synchronizing the table that
had any changes to it will disappear when access is reopened. Now I do not
fully understand how this is possible with out actually seeing it happen. I
was just wondering if any of you guys have ever experienced this or know what
the cause of this problem is.

Thanks,
akphidelt

 

[Arvin Meyer [MVP]]

I have never experienced it, but a client of mine swears he lost some
changes that way. The biggest problems in replication are caused by
replicating and unsplit database or a front-end of a split one. You are
guaranteed to eventually have a problem with corruption. The second biggest
problem that I've seen is replication over a dial-up connection when the
connection drops. Actually, any connection can drop, so it's important to
only replicate over a stable connection. That means no dialup, or air cards,
or WiFi cards, and a stable network without any CRC errors.

Try creating a new Design Master. That is usually the best (and often only)
way to handle problems due to corruption. If you need more information, it
might be a good idea to use the replication newsgroup.

micrososft.public.access.replication

 

[David W. Fenton]

I have never experienced it, but a client of mine swears he lost
some changes that way. The biggest problems in replication are
caused by replicating and unsplit database or a front-end of a
split one. You are guaranteed to eventually have a problem with
corruption. The second biggest problem that I've seen is
replication over a dial-up connection when the connection drops.
Actually, any connection can drop, so it's important to only
replicate over a stable connection.

Er, DIRECT replication is only suitable for wired connections of
greater than 10Mbps bandwidth. For WANs or wireless connections, you
have indirect and Internet replication. The reason why DIRECT
replication is not suitable is the same reason you can't run a split
app with the back end on the other end of a dialup or WAN connection
-- it's because the remote MDB has to be opened across the wire,
i.e., its data pulled across the wire to the RAM on the local PC.

Indirect and Internet replication don't do that, and that's why they
are safe.

That means no dialup, or air cards,
or WiFi cards, and a stable network without any CRC errors.

Bandwidth is important, too. An old-fashioned coax network would
probably be too slow, as well (just as it probably would be for a
split app with the back end across a coax network connection).

Try creating a new Design Master. That is usually the best (and
often only) way to handle problems due to corruption. If you need
more information, it might be a good idea to use the replication
newsgroup.

It depends on what kind of corruption it is. If a single replica
gets corrupted, then you should just discard that replica (and
delete it from the replica set, of course), and then create a new
replica to replace it. This assumes, of course, that the data in the
corrupt replica has been synched with the other replicas.

It's only when the replication structures themselves have become
corrupted and the replicas can't synch that I'd start a new replica
set.

 

[David W. Fenton]

Apparently they did something where when after synchronizing the
table that had any changes to it will disappear when access is
reopened. Now I do not fully understand how this is possible with
out actually seeing it happen. I was just wondering if any of you
guys have ever experienced this or know what the cause of this
problem is.

What do they mean "disappeared?"

Perhaps a table link got deleted?

Perhaps a table has been marked HIDDEN.

There is no reason why a table would ever be deleted in a normal
synchronization operation, unless the table had actually been
deleted from the Design Master.