"Leslie Isaacs" < XXXX@XXXXX.COM > wrote in
Replication is not a solution for performance or application design
problems. Its sole purpose is to provide updatability of one back
end data file in more than one location such that the changes can be
synchronized so that both files are identical after the synch. In my
opinion, the only place this is appropriate today is for laptop
users who need live data out in the field without a full-time
You need to redesign your app, which is the source of your problems.
It might that the particular problems would not even be resolved by
replication. Indeed, the "too many databases" problem is greatly
aggravated by replication, which requires the opening of even more
tables in the background than non-replicated apps.
So, in short, no -- replication is not the answer to your problem at
David W. Fenton http://www.yqcomputer.com/
usenet at dfenton dot com http://www.yqcomputer.com/