replication is not complete

[Guest]

I have made a replication from a design master, but the replication only
contains the tables and queries, not the forms, macros, reports and modules.
This also means that I can not use the replica because the switchboard is not
there. I can not import the missing objects, because it is a replica....

 

[Arvin Meyer [MVP]]

Replication is really only designed for data. Any other usage will result in
corruption or unpredictable behavior. Databases should be split into a
front-end, containing the application linked to a back-end containing only
the data tables. The switchboard table, being local in nature, is left as a
non-linked table in the front-end. If you use replication that way,
everything will work as you expect it to.

 

[Douglas J. Steele]

Realisitically, replication is only intended for data, not application
objects such as forms and reports.

What you should do is split your application into a front-end (containing
the queries, forms, reports, macros and modules) and a back-end (containing
the tables and relationships). Only the back-end should be replicated. To
ensure everyone has the current front-end, simply give them a copy of it.

 

[David W. Fenton]

I have made a replication from a design master, but the
replication only contains the tables and queries, not the forms,
macros, reports and modules. This also means that I can not use
the replica because the switchboard is not there. I can not import
the missing objects, because it is a replica....

Arvin has answered the question -- replication is only for pure-Jet
objects (tables, queries).

The switchboard problem is a mistake made by the database splitter.
The switchboard wizard creates the switchboard table in the front
end and it should be left there.