Hi Karen.
Yes it is possible to have Access subscribers:
see http://msdn.microsoft.com/library/en...lctem_0815.asp
And the Access DBs should be subscribers and the SQL server would be the
Publisher.
And YES switch to the MSDE instead of Access, for a lot of reasons.
(Compatibility, flexibility, openness in regard to debugging and error
logging, stability)
HTH
JorgenD.
"Karen Middleton" wrote:
> Hello All
> We have a computer based application running on trucks and they
> capture the transaction into a Access database we need to collect the
> data from multiple trucks into a SQL Server database centrally.
> Can somebody please explain whether Access can replicate to SQL Server
> with Access as publisher and SQL Server as the subscriber. Also, I am
> wondering is it worthwhile to replace Access by MSDE since MSDE is
> free I would appreciate your feedback on this count.
> Also, any books, web sites, white papers and how to setup a
> replication from Access to SQL Server. Also, can somebody please
> explain how the replication works from Access to SQL Server and is it
> lot of coding to get this working and what kind of replication is it
> full table or delta replication.
> Also, some of our trucks will be in far off places is there a nice way
> in which Access can be made to replicate from these remote sites to
> the central site what kind of comms do we need.
>
> Many thanks in advance for your inputs
> Thanks
> Karen
>
Karen,
I agree with Jorgen that MSDE would be preferable long-term. However, your
original question was about having Access as a publisher and SQL Server as a
subscriber, which is not available out of the box using Jet. If you have sql
server as a merge publisher and access as a subscriber, in many senses
datawise it will be functionally equivalent, but care will need taking with
administrtion and conflict resolution where the role of the publisher is
indeed distinct to the subscriber.
HTH,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment