Portable database

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ray - 26 Jun 2005 12:12 GMT

I would like to create a database and require the users to enter the data
from their NB. Then sent back to me for consolidation. I got an idea to
use replication for this purpose. Can someone advise me the actual
procedures to create such database.

Thanks,

Ray

Reply to this Message

Jack MacDonald - 26 Jun 2005 14:17 GMT

Replication will work for this situation *IF* some conditions are met:

1 - the notebook computers MUST connect to the network where the
consolidation database exists. Using floppy disks or other removeable
media to move the files (including email) is not acceptable. Dialup
access may be acceptable. Your requirement that users "... send it
back to me..." is a indication that you might NOT be able to use
replication.

2. - replicate ONLY the backend side of a split application. Do NOT
replicate forms, queries, reports, etc

3. - for WAN connectivity (including dialup) to work properly, you
must use Indirect Synchronization which is available only through
Replication Manager which is a component of the Office Developers kit.
Direct Synchronization using stock Access is insufficient for anything
other than direct LAN connectivity.

4. - do not use your Design Master for data entry. Keep it in a safe
location, away from day-to-day activity, and synchronize it only as
required (including often enough to stay within the Retention Period).

5. - do NOT move a replica from its original location once it has been
created.

Having set the ground rules, you should experiment with a COPY of your
database because it is real easy to corrupt your database when
learning the steps. Then just follow the menus to:

- make your Design Master

- make several replicas in their appropriate location. A "working"
replica on the central computer should act as a "hub" for all the
mobile computers to synchronize with. It could also work as the
LAN-based replica that LAN-based users would interact with.

- edit any of the replicas, including the hub replica

- synchronize the replicas (e.g. with the hub replica) to propogate
the changes throughout the replica set.

Since you will be synchronizing the backend portion of a split
application, you will need to either:

- train your users how to open the backend directly to synchronize
with the hub, OR

- write some VBA code in the frontend to synchronize the backend with
the hub.

Cross that bridge when you come to it.

>I would like to create a database and require the users to enter the data
>from their NB. Then sent back to me for consolidation. I got an idea to
[quoted text clipped - 4 lines]
>
>Ray

**********************
jackmacMACdonald@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

Reply to this Message

David W. Fenton - 26 Jun 2005 21:11 GMT

> - make several replicas in their appropriate location. A "working"
> replica on the central computer should act as a "hub" for all the
> mobile computers to synchronize with. It could also work as the
> LAN-based replica that LAN-based users would interact with.

Actually, I'd disagree with that -- it's better for the hub replica
to *not* be in production use, because if a synch happens while a
user is editing data, it can cause updates to not be applied, and,
in the case of memo fields edited in bound controls, it can cause
corruption of the memo pointer (and subsequent loss of the record).

Signature

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

Reply to this Message

Jack MacDonald - 28 Jun 2005 04:48 GMT

You're right -- my mistake.

>> - make several replicas in their appropriate location. A "working"
>> replica on the central computer should act as a "hub" for all the
[quoted text clipped - 6 lines]
>in the case of memo fields edited in bound controls, it can cause
>corruption of the memo pointer (and subsequent loss of the record).

**********************
jackmacMACdonald@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

Reply to this Message