Why not have forms in a replica?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Why should I not have forms in Replica's?
I have it right now and it works fine, but of coarse you never know what
will happen! So I am considering splitting the database. So if anyone knows
why this is important I would be greatful.
 
more traffic, more chance for corruption, and because that is not what
replication was designed to replicate. If you need to change the forms,
just send out a new FE to the users.

If you are in a multi-user environment (and you must be since you are using
replication), you are asking for corruption of your data if you do not split
the db.

I have personal experience of the forms replication corrupting data (back in
Access 97). You don't want that sort of RGE (resume generating event) on
your "task" list

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.

www.experts-exchange.com - experts compete for points to answer your
questions
 
Why should I not have forms in Replica's?
I have it right now and it works fine, but of coarse you never know what
will happen! So I am considering splitting the database. So if anyone knows
why this is important I would be greatful.
Click to expand...

In my experience, replicating a database which contains Forms causes
excessive bloating of the size of the database. By all I've read (see
MichKa's comments at www.trigeminal.com) it also makes the database
much more vulnerable to corruption.

John W. Vinson[MVP]
 
Thank you all three, I will now convince my client that I need to split the
database, and only replicate the tables ;-)
Camilla
 
Thank you Kevin, I have now printed it and have it on my wall. I do use a
lot of look-up fields (which I should abhor according to commandment #2).
Why are they the art of the Evil One?
 
OK, if that is the only evil, I can live with that. I thought perhaps it was
a good idea, because I only store a number, and the lookup fields are in some
instances pretty long (not specified by me, but it is what the client wants
to be able to look-up!!).

Thanks again for the promt reply.
 
Hello everyone,

I'm reading "Access 2002 Enterprise Developer's handbook" and it says to
split the database & replicate both the back-end and the front-end and
distribute the replica's on a WAN.

Comments please?


--phill
 
Hello everyone,

I'm reading "Access 2002 Enterprise Developer's handbook" and it says to
split the database & replicate both the back-end and the front-end and
distribute the replica's on a WAN.

Comments please?
Click to expand...

If it does say that - page citation?? - I'd have to disagree. MichKa
is *the* expert on replication and warns in the strongest terms not to
replicate code-bearing objects.

Since there is (usually) no data in a frontend, and since (hopefully!)
users aren't going to be making any structural changes which should be
replicated to other users, I'd argue for replicating the DATA in the
backend; and distributing a clean unreplicated frontend to each user
(with code to relink it to that user's replica of the backend). If the
frontend is in the form of a MDE that's all the better.

John W. Vinson[MVP]
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Access 2007 replica to master 4
Access convert ms access 2007 database replica to design master 2
Changing a replica to a Design Master 2
How do you efficiently remove a replica from a replica set? 0
Two replicas are from different replica sets and cannot be synchro 10
Help! What type of replica do i need to create? 1
Design Changes cannot be applied to replicas 1
Splitting a replica set 1

Back
Top