RE: convert replica

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: robirdman (robirdman_at_discussions.microsoft.com)
Date: 12/07/04

  • Next message: Jim Clark: "Migrating replicated database to new Windows 2003 server" 
    Date: Tue, 7 Dec 2004 04:43:02 -0800

    This sounds so incredibly complicated. I did not understand all of your
    post. You didn't say if I need to import the tables (57) nor queries (197).
    I'll have to read up on creating links. Just one table has 27 data fields.
    I can't imagine why it should be made so difficult and what is the purpose of
    the "create design master" menu. I guess if I did it gradually over a period
    of days it wouldn't be as terrible. I don't know when I'll have that much
    time.

    "Paul Sanguinetti" wrote:

    > When all else fails, try creating a new database. Import all
    > forms/macros/reports/modules etc. Then create links from the new database to
    > the old database. Finally, use create table queries to copy the data fields
    > from the old database to the new database. Don't use "Select *" as that will
    > also copy the replication information and you will still have the problems
    > associated with a replica. You'll have to select each valid data field
    > individually in the query. After you've finished copying a table, delete the
    > link to the old table and rename the new table to the proper (old) table name.
    >
    > Its tedious, but the only way to convert a replicated database to a simple
    > non-replica.

  • Next message: Jim Clark: "Migrating replicated database to new Windows 2003 server"

    Relevant Pages