I've just started working with a new client. They have a database
created by self-taught users. It's been in use for many years. It's used
by one person in the US, and one person in Canada. Each has a
stand-alone copy of the database (no split into front end & back end).
They use replication on a regular schedule to keep the two copies
synchronized.
Every time the database is opened, it automatically goes through some
sort of "Repair". This happens when I open a copy of the database on my
computer, too. I made a copy of the database by opening a blank database
and importing all tables, queries, etc. to it. When I open this copy,
there is no "Repair."
Any thoughts as to why there's a "Repair" every time the DB is opened? I
haven't worked with replicated DB's before - is it something to do with
this? (Any pointers to a good overview of replication or alternatives
for synchronizing two DB's at distant locations?)
Thanks in advance
Sigurd Andersen
Tidak ada komentar:
Posting Komentar