> We have a time accounting application with 5 tables. We want to allow
> the agents to keep their time on their systems off-line and then
> replicate when they get back to the office OR via the internet.
>
> While Michael R. Hotek's replication primer
> {http://www.mssqlserver.com/replication/primer_p1.asp}
> was enlightening, I'm not sure if that is overkill or not.
>
> Any thoughts?
>
> Our application is written in Delphi with ADO as the DB layer.
> If you can give me options on how to get this thing done using this
> environment that would help, too...
>

"Paul Ibison" <anonymous@discussions.microsoft.com> wrote in message
news:b3d401c3ecef$071ac680$a101280a@phx.gbl...
> Difficult to give a simple answer to this as it is a big
> field and a wide question! It sounds from the second email
> as though your 5 agents are entering data themselves from
> a disconnected environment and the number of articles is
> 5. Such a scenario lends itself to (A) merge replication
> or (B) transactional replication woith queued subscribers.
> My choice is usually merge (pull subscriptions) in this
> case as there is a bigger choice of conflict resolvers.
> This is another question to raise - can subscribers
> potentially modify the same data? (1) If so, conflicts
> could arise and you'll need to investigate this. (B) if
> not, you'll need to investigate distinguishing between
> subscribers in order to partition the data. There are
> various ways to do this and I don't want to get too
> specific here as your question is preliminary. So, hope
> this helps and no doubt there will be more questions
> coming up.
> Regards,
> Paul Ibison