How do I replicate an application that has implemented split data and code MDBs?
You can replicate the application database, the table database, or both. However, you may find it more efficient in practice to only replicate the table database. Although design changes are replicable, synchronizing them can cause problems. There have been reported instances of design changes to forms and modules not propagating successfully to all replicas in a replica set. If possible, develop your application fully before replicating and distributing it. If you need to make design changes later, then distribute the front-end database separately from the tables. • How do I compact a replicated database? When compacting a replica in Microsoft Jet Database Engine 3.5x, there are four issues to keep in mind: • Make sure the replica is copied back to the original location/name after the compact and before synchronizing with any other replica. If you don’t, then you’ll be adding another replica to the replica set and if the replica is the Design Master, it’ll no longer be the Design Mast
Related Questions
- I already have data processing application that should also take care of label printing. How can I integrate bar code label printing in my application?
- When using the HT9020 datasheet application circuit to interface to the telephone line, why can I not decode CPT data?
- When building an application, how can I locate a code section or data section at a specific absolute address?