Is it possible to replicate a database before close ?
I want to that with VBA code if possible but don't
know how to do.
Can anyone help me ?

Has anybody successfully implemented Internet Replication with Access 2002?
If so, is it necessary to have MOD packaged with Replication Manager in
order to make it work?  If Replication Manager is not necessary, how is it
done without it?

I have a form that has a button that will synch the replica to the
design master. (export)
When I run the code (pasted below... strDBName is the replica and
strSyncTargetDB is the design), I don't get the conflict wizard to

I just starting getting a  Run-time error '-2147467259 (80004005)'  while
updating using JRO on Windows XP computers.  I have no problems running an
update on other OS, such as 98SE, NT or 2000.
Any suggestions on how to correct this problem?

I have a replicated database, with a Design Master and
three Replicas, and I use Replication Manager to synch
them at night.
From time to time I make updates to the Design Master. For

Does anyone know whether this scenario would be "safe":  machine A
runs O2k, and Replication Manager, & manages base replica built with
2000.  Machine A places and manages data entry replica on machine B,
which is running 2003.

We have a number of replicas that need synch at the end of each day.  Is
there a way to automate or upadate all without having Replication Manager?
As we do not have a IT person we are forced to do the process ourselves and
it has become very time consuming.  Any help would be ...

I have a client using MS 2003 and creating replications
of the tables.  They tell me that when they do a compact
and repair, the tables become unreplicable.  
Is it true that when you do a compact and repair that the

I'm trying to run the datasplitter wizard on a database.
When I run it, I get the message "Can not run datasplitter on a replica."
But the database is not a replica.  It doesn't say design master in the
title window, tho "create replica" is a choice on a menu (I suppose at some

I'm getting rather frequent crashes from the Access 2003 replication
conflict viewer.  I recently synchronized two Access 2000 format
databases from Access 2003.  During this synchronization, a design
change was propagated from one database to the other (a field was

I have 4 partial replicas, each representing an office's
records.  When an office wants to move a record from one
office to the next (make it the responsibility of another
office), the record does get added to the new office's

Please Help Me!
a few design changes were recently needed on my
(replicated) database. I synchronized the production DB
with the design master before getting started, with no

I have a db that is split.  The back-end has the tables.  
I would like to replicate both since I don't want users in
other cities to have to access our LAN system to use the
tables (since it will cause the db to act slower).  But in

I want access to create replicas only with absolute path names
\\Laptop\C\database.mdb
the database server name is stored with //server/database.mdb , but the
replica on my computer (Access2000 /Win XP) comes only with a relative path

When I enter data from both my replica and master, the autonumber fields are
completely random (as far as i can tell: -1010384 then 4838221 for example).
Does anyone know why this would happen or at least how to resolve it?
Thanks!