On Wed, 14 Sep 2005 09:33:01 -0600, "Danny J. Lesandrini"
<dl*********@hotmail.com> wrote:
I suspect this isn't possible, but I recently moved a app to SQL Server
and it contains a Project table. Now I have a new CRM tool that needs
to be mobile, but should also synch with the Project table on SQL Server.
I really like the idea of replicating an Access database for the mobile
users and somehow synching with the SQL server for the Projects. Is
that doable?
Sure it's doable. It's not all that hard either, but first you need
to decide _what_ type of replication you want to do. I'm not up on
all the current terms for replication, but the 2 basic types are what
I call "Forward only" and "Merge". Forward only is pretty much just
what it means. The "central data store" pushes information out, but
won't accept any back. In "Merge" type replication, information goes
both ways.
The real trick with replication is deciding "who wins" in collision
occurrences. Replica A downloaded information from the Master at
Noon. The Master was then updated with information from Replica B at
1PM. If Replica A wants to update that same bit of information at
2PM, do you allow it?
Once you decide that, it's easy! (He says with a smile on his
face....)
Personally, I think that unless the users are going to be _really_
offline, Replication isn't worth the effort anymore. Just design a
web-based interface for users to use and be done with it. Everyone
gets the most up-to-date info all at the same (more or less) times.
There is still, always, the occasion when someone is going to start
editing a record, then go off to lunch (or whatever) and finish when
they get back (not knowing someone else has already updated
something), but then that's always a problem in multi-user databases
even when replication isn't thrown into the mix.
--
Drive C: Error. (A)bort (R)etry (S)mack The Darned Thing
