Replication Strategy

I have an app that has this design: MasterDB contains all the templates used
by the app and a record of all DealDB's created, DealDb contains just the
data, imported from various sources. A new DealDB is created for every new
"deal". The app works fine in the office, now I want to extend it for out of
office(in-transit) use. My idea is to install MSDE on the users PC's and:
1. When the deal is marked in-transit the app will not allow anyone in the
office access to it. So, I want to either detach/attach the DealDB to the
local MSDE or use Bacup/Restore to local MSDE and the same coming back to the
office. Is one better/safer/less error prone then the other? Can I attach a
DB if it was never detached/ can I restore a DB to server that was not the
one it was backed up on?
2. The MasterDB will have to be replicated to local MSDE when a user puts a
deal in-transit. When the user is back in the office all changes to the
local(MSDE)MasterDB will need to be replicated back to the network version.
While the DealDB will simply be either attached or restored back to the
network.
I guess I would use merge replication for the MasterDb? Going to local would
I use Push or Pull subscription, and what about going back to network Push or
Pull?
Can someone help me out with the details, is there a script I can use?
Thanks!
Yes you can set transformations in transactional replication
"mikeb" wrote:

> I have an app that has this design: MasterDB contains all the templates used
> by the app and a record of all DealDB's created, DealDb contains just the
> data, imported from various sources. A new DealDB is created for every new
> "deal". The app works fine in the office, now I want to extend it for out of
> office(in-transit) use. My idea is to install MSDE on the users PC's and:
> 1. When the deal is marked in-transit the app will not allow anyone in the
> office access to it. So, I want to either detach/attach the DealDB to the
> local MSDE or use Bacup/Restore to local MSDE and the same coming back to the
> office. Is one better/safer/less error prone then the other? Can I attach a
> DB if it was never detached/ can I restore a DB to server that was not the
> one it was backed up on?
> 2. The MasterDB will have to be replicated to local MSDE when a user puts a
> deal in-transit. When the user is back in the office all changes to the
> local(MSDE)MasterDB will need to be replicated back to the network version.
> While the DealDB will simply be either attached or restored back to the
> network.
> I guess I would use merge replication for the MasterDb? Going to local would
> I use Push or Pull subscription, and what about going back to network Push or
> Pull?
> Can someone help me out with the details, is there a script I can use?
> Thanks!
sql