Hello Alan,

You may want to refer to the following steps to see if this works for you

1) Create the publication. Before creating ANY subscriptions follow these
BOL steps:

Topic: How to configure a publication to allow copying of subscription
databases
(Enterprise Manager)

Create the publication using the Create Publication Wizard.

In SQL Server Enterprise Manager, expand the Replication and Publication
directories, and then right-click the publication that you want to enable
for new
subscriptions.

For snapshot replication and transactional replication, click the
Subscription Options tab in the Publication Properties, select Use a
Distribution Agent that is
independent of other publications from this database, and then select
Snapshot files are always available to immediately initialize new
subscriptions. You do not
need to do anything for this step if you are using merge replication.

Select Allow new subscriptions to be created by attaching a copy of a
subscription database.

2) Create a PULL subscription to the newly created publication. Use all the
properties that you will want copied to future PULL subscriptions.

3) Make a copy of the subscription database/subscription (from the
subscriber perspective) by following BOL:

Topic: How to copy a subscription database (Enterprise Manager)

On the Subscriber, in SQL Server Enterprise Manager, expand the Replication
and Subscriptions directories, right-click the pull subscription that has a
subscription database you want to copy, and then click Copy Subscription
Database.

In the Copy Subscription Database dialog box, browse to the directory or
drive where you want to save a copy of the subscription database.

The location can be on the network, using removable media (such as CD-ROMs
or tape devices) or on a File Transfer Protocol (FTP) site.

In the File Name box, type a name for the subscription database file (the
file will have the extension .msf).

4) Attach the subscription database to a new instance or remote server (at
least if you are using a different instance, so for a new instance you have
to type
or cut/paste the entire path to the msf file). The msf file must be local
because will actually be attached, not copied or uncompressed. Follow BOL:

Topic: How to attach a subscription database with named subscriptions
(Enterprise Manager)

On the new Subscriber, in SQL Server Enterprise Manager, expand the
Replication directory.

Right-click the Subscriptions directory, and then click Attach Subscription
Database.

Either type the Universal Naming Convention (UNC) path or click the browse
(...) button and browse for the location of the .msf file.

In the Name of database to create box, type a name for the database.

5) Right click on the original pull subscription (the one you copied from).
Choose to generate a script to create the subscription. Edit these
parameters in the
sp_addsubscription statement from the "Script to be run at Publisher":
"@subscriber = N'Publisher\Instance', @destination_db =
N'NewSubscriptionDBName'," . Run the
edited sp_addsubscription at the publisher. There is no need to run the
"Script to be run at Subscriber" as that information was added with the
attachable subscription step.

Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================


This posting is provided "AS IS" with no warranties, and confers no rights.