Synchronization

[B]

I run a small company and I have a telemarketing program that I built over
the past 5 years and it works great! However, we are growing. I have sales
reps in several states and I have appointment setters and everyone is
geographically separated. Each sales rep has his or her own DB and
appointment setter and they share data through a P2P network. I want to
replicate the databases so 2 or 3 appointment setters can work from the same
program, right now we play hot potato and that isn’t efficient. I have
appointment setters that could be working on someone else’s appointments but
they can’t because the data they create will be lost. I want one appointment
setter setting appointments for Tuesday and at the same time I want another
appointment setter setting for Wednesday and at the end of the day the sales
rep will synchronize data. What is the best way to do this?

Specifics: The data base has hyperlinks to PDF files so everyone has their
program in a folder directly under C: drive, this keeps the hyperlinks
working regardless of who has the program. There are only a few tables that
change on a daily basis, applicant, call result and appointments. I think I
have too many sub forms and functions to do a web based call form.

My solution would be to create 3 folders in the main folder on C drive and
put the design master in one and the replicas in the others (don’t know if
the hyperlinks would work, if I did this). Next, I would have the agent
download each replica folder from each appointment setter using the P2P and
then synchronize the data.

Any suggestions on a easier way to do this or do you see any problems with
this solution? I never made a replica before. At this point dumping a ton
of cash into a server system is not an option but if this is your solution I
would like to hear it because it won’t be long before that will be an option;
however, keep in mind I have to find a temporary fix.

 

[Aaron Kempf]

you should just use Access Data Projects and keep everything on a server
no more compact & repair
no more 2gb limit

no more crapping out
no more bouncing file servers to update your database

 

[Larry Daugherty]

Look in Access help for Replication. There is also an access
newsgroup devoted to replication.

HTH

 

[David W. Fenton]

I run a small company and I have a telemarketing program that I
built over the past 5 years and it works great! However, we are
growing. I have sales reps in several states and I have
appointment setters and everyone is geographically separated.
Each sales rep has his or her own DB and appointment setter and
they share data through a P2P network. I want to replicate the
databases so 2 or 3 appointment setters can work from the same
program, right now we play hot potato and that isn?t efficient. I
have appointment setters that could be working on someone else?s
appointments but they can?t because the data they create will be
lost. I want one appointment setter setting appointments for
Tuesday and at the same time I want another appointment setter
setting for Wednesday and at the end of the day the sales rep will
synchronize data. What is the best way to do this?

It depends on what network connections are available. If you can
have the users synch to a LAN each time they are in the office, it's
very easy to implement with direct replication.

If they have to synch over an Internet connection, it's much more
comlpicated,t hough completely doable.

Specifics: The data base has hyperlinks to PDF files so everyone
has their program in a folder directly under C: drive, this keeps
the hyperlinks working regardless of who has the program.

How do the PDFs get to all the users? That is, won't the hyperlinks
be valid on only one user's PC?

There are only a few tables that
change on a daily basis, applicant, call result and appointments.
I think I have too many sub forms and functions to do a web based
call form.

Huh? Your application shouldn't be replicated, only the data tables.
That is, you should split the app into two files, one with the
forms/reports/etc., and another with the data tables and nothing
else. Only the back end data file should be replicated.

My solution would be to create 3 folders in the main folder on C
drive and put the design master in one and the replicas in the
others (don?t know if the hyperlinks would work, if I did this).
Next, I would have the agent download each replica folder from
each appointment setter using the P2P and then synchronize the
data.

No, this is not at all the way you would do it. Replication works by
synchronizing IN PLACE, where the editing takes place.

You'd put your Design Master away somewhere safe, because it should
not be involved in daily synchronization or editing activities
because it is a special replica whose purpose is making DESIGN
CHANGES to the data tables, and nothing else. You need only
synchronize with one of the other replicas often enough to keep the
DM from expiring (the default retention period is 1000 days).

Secondly, you don't want copies of all the replicas.

You want a central computer that is functioning as a server to have
one replica, which will be the synchronization hub.

Each laptop will have a replica.

And the users of the laptops will edit their local replica.

They they will synch with the synch hub on the server.

Any suggestions on a easier way to do this or do you see any
problems with this solution? I never made a replica before. At
this point dumping a ton of cash into a server system is not an
option but if this is your solution I would like to hear it
because it won?t be long before that will be an option; however,
keep in mind I have to find a temporary fix.

You don't need a server to use Jet replication -- I have plenty of
clients doing it without a server.

But you do need a workstation that is *acting* as a server, at least
part of the time.

 

[David W. Fenton]

you should just use Access Data Projects and keep everything on a
server no more compact & repair
no more 2gb limit

no more crapping out
no more bouncing file servers to update your database

Did the original poster say that he had any of these problems?

If not, then why are you proposing:

1. spending a couple thousand on installing a server with SQL Server

2. spending the time and money to convert the app to use SQL Server

3. spending the time and effort to install SQL Server on the laptops
and setting up some kind of synchronization procedures.

You are an idiot, Aaron -- you have one solution to everything, no
matter whether it makes any sense or not.

And so far, you are batting 0.000 in terms of identifying scenarios
where your advice is helpful.