Is it possible to make a table replicable thats already been created

mctaguma

Registered User.
Local time
Tomorrow, 09:05
Joined
Dec 30, 2006
Messages
18
I have tables in a database that are not ticked replicable at present (tick button is greyed out), this is causing
the records in the table to become scrambled when we attemp to replicate the database.

Any advice please, with over 50 tables in the database we don't feel inclined to start from scratch.

Any help appreciated.

Matthew
 
If you are opening it from the MASTER BACKEND where the tables are actually located you SHOULD be able to mark them replicable. However, if you haven't synched with all replicas, then it might not let you.
 
boblarson said:
If you are opening it from the MASTER BACKEND where the tables are actually located you SHOULD be able to mark them replicable. However, if you haven't synched with all replicas, then it might not let you.


Part of the database was already bult by somebody else, tables were not made replacable and a design master was not made.

Here is link to the database, not sure if anybody can help

http://www.scoutingtimaru.org.nz/dbtest/Copy%20of%20Copy%20of%20mods%20hidden%20modSecurity%20working%20Copy%20of%20Age%20foujnd%20Copy%20of%20Cub%20errors%20and%20member%20scroll%20fixedCompile%20and%20colurs%20working,data%20added%20%20Access%202000%20Training%20full%20delete%20Working%20Copy.mdb

Matthew
 
Some info for you while I look at your db. If your database is replicated, then there IS (or WAS) a Design Master. You can't get a replicated database without a design master. There can only be one designated design master at a time.

Now that I've looked at your database, I can see that it is not a replica, it isn't associated with a replica. In order for it to be you have to create a replica from this, you need to select Tools>Replication>Create Replica and then it will prompt you if you want to save a backup of the original. Say yes and then it will create a replica and the current one will become the design master. At that point your checkbox for replicable will become available and you can actually choose to UNCHECK any boxes you don't want replicated. The next time you synch it will remove them from the replicas.
 
boblarson said:
Some info for you while I look at your db. If your database is replicated, then there IS (or WAS) a Design Master. You can't get a replicated database without a design master. There can only be one designated design master at a time.

Now that I've looked at your database, I can see that it is not a replica, it isn't associated with a replica. In order for it to be you have to create a replica from this, you need to select Tools>Replication>Create Replica and then it will prompt you if you want to save a backup of the original. Say yes and then it will create a replica and the current one will become the design master. At that point your checkbox for replicable will become available and you can actually choose to UNCHECK any boxes you don't want replicated. The next time you synch it will remove them from the replicas.

I followed your instructions, and the data is still scrambled (record order changed), any other suggestions?

Matthew
 
Tables don't store data in any particular order. If you want to display it in a meaningful order, then you have to use a query and select a field to sort on.
 
Bob,

Thanks for the help, will putting in a auto number field with primary key work do you think, into each of the LUtables?

Matthew
 
That still will not order your tables. Regardless of an autonumber (which only guarantees UNIQUENESS, not consecutive numbers) or even another Primary Key, it does not store data in any sorted order. While it may LOOK like it at times, it really doesn't. So, if you want to see it in any order, then adding a field to sort is fine, but be aware that if you use an autonumber, that doesn't guarantee it will sort the way you think it will. If you wind up using replication, your autonumbers will now become things like -123347889 or 2389340, etc.
 

Users who are viewing this thread

Back
Top Bottom