Confused Sending Order Confirmation

So, I've gone through the BOL walkthrough and all looks great however, I am confused about how to extend my application to send an order confirmation that contains an order header and order detail. I also have Shyam Pather's book but haven't seen this discussed yet. Does it make sense to do two inserts in my subscription? Something like "insert into orderedAlertHeader" and "insert into orderAlertDetail"? Can I create more than one table for the same subscription?

I think I've been looking at this for too long.

TIA

Ian

For those who are curious I think I've figured out a way to accomplish what I needed. I ended up creating an XML column on my alert table that I can load my detail into. My formatter then can do whatever I need it to.

I'll give an example if someone is interested.

Conflicts due to table order

Merge replication, SQL 2000. Does anyone know if there is a problem with
syncronizing caused by the physical order of the inserts/updates in related
tables? I am getting some conflicts that indicate a failure due to "...
Referential integrity rules require a related record in the table
'<tablename>'
When I check the tables on the publisher they are all there and fine, but
when a laptop user tries to synch they get the above message and the related
table records do not get added.
David
Modify your tables so that each constraint has a not for replication clause
on all constraints.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"David" <dlchase@.lifetimeinc.com> wrote in message
news:OmfYQNuIHHA.3952@.TK2MSFTNGP02.phx.gbl...
> Merge replication, SQL 2000. Does anyone know if there is a problem with
> syncronizing caused by the physical order of the inserts/updates in
> related tables? I am getting some conflicts that indicate a failure due
> to "... Referential integrity rules require a related record in the table
> '<tablename>'
> When I check the tables on the publisher they are all there and fine, but
> when a laptop user tries to synch they get the above message and the
> related table records do not get added.
> David
>
|||When I look at table properties and the Relationships tab, it has the box
checked "Enforce relationship for replication". Is that what you are
referring to...and if so, do I uncheck it?
Also, I assume I will need to completely re-create all merge publications to
the laptops?
David
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ulOPb%23xIHHA.1252@.TK2MSFTNGP02.phx.gbl...
> Modify your tables so that each constraint has a not for replication
> clause on all constraints.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "David" <dlchase@.lifetimeinc.com> wrote in message
> news:OmfYQNuIHHA.3952@.TK2MSFTNGP02.phx.gbl...
>
|||Yes, that is it. I think you will need re-create all publications and
subscriptions.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"David" <dlchase@.lifetimeinc.com> wrote in message
news:u$G8sG8IHHA.4712@.TK2MSFTNGP04.phx.gbl...
> When I look at table properties and the Relationships tab, it has the box
> checked "Enforce relationship for replication". Is that what you are
> referring to...and if so, do I uncheck it?
> Also, I assume I will need to completely re-create all merge publications
> to the laptops?
> David
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ulOPb%23xIHHA.1252@.TK2MSFTNGP02.phx.gbl...
>