Instant Replication?

[Patrick A]

All,

I'm facing a situation where an application (D3) that gets information
from my DB takes 4-5 times as long to process records when a user is
in the DB.

As I see it, one potential solution to the problem is to set things up
so that I use one DB for D3, and another for data entry (DE) and keep
the two db's synchronized.

If I decide to go that route, what is the simplest, easiest and safest
way to update the D3 database when a user exits the DE database?

My database is a 10-15 MB Access 2000-2003 DB.

I have 10-15 users.

All suggestions welcome.

Thanks,

Patrick

[David W. Fenton]

Patrick A <pa*****@stradley.comwrote in
news:7c**********************************@d62g2000 hsf.googlegroups.co
m:

I'm facing a situation where an application (D3) that gets
information from my DB takes 4-5 times as long to process records
when a user is in the DB.

As I see it, one potential solution to the problem is to set
things up so that I use one DB for D3, and another for data entry
(DE) and keep the two db's synchronized.

If I decide to go that route, what is the simplest, easiest and
safest way to update the D3 database when a user exits the DE
database?

My database is a 10-15 MB Access 2000-2003 DB.

I have 10-15 users.

Replication is not suitable for solving performance problems -- it
would just add needless complexity and additional vulnerability to
your setup.

Figure out what's causing the slowdown and fix it. Period.

Tony Toews's performance FAQ is a great place to start:

http://www.granite.ab.ca/access/performancefaq.htm

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/