Replicating with Access in Hilary's book

On page 50, you discuss replicating SQL Server to Access. Two questions:
1. While you discuss all 3 replication types, it sounds like you are
recommending Merge as the solution?
2. In the hint, it says in part, "all transactions occuring on the Merge
Subscriber [Access] will be "published" or merged to the SQL Server
database." Do you mean the transactions are merged on the SQL Server's
schedule (both directions?) or via some user interaction on the Access side?
1) while you can use snapshot, transactional, or merge replication; what I
was trying to get at was that many people want the access database to
publish to sql server, and I was suggesting that you could set up the access
database as a subscriber and if all the changes originate there it could act
as the publisher.
2) All transactions will be merged with the publisher, but they all
originate with the subcriber/access database. the synchronization will be
kicked off each time the push agent runs - I don't believe you can do a
pull.
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
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:%239ZFAV2cFHA.1044@.TK2MSFTNGP10.phx.gbl...
> On page 50, you discuss replicating SQL Server to Access. Two questions:
> 1. While you discuss all 3 replication types, it sounds like you are
> recommending Merge as the solution?
> 2. In the hint, it says in part, "all transactions occuring on the Merge
> Subscriber [Access] will be "published" or merged to the SQL Server
> database." Do you mean the transactions are merged on the SQL Server's
> schedule (both directions?) or via some user interaction on the Access
> side?
>