Hi John,
My advice is that if you have SQL Server use it.
It does depend on how many users you have but Access really was not designed
to cope with lots of concurrent users.
You can use Access Replication but that could be slow depending on the
amount of data you need to replicate and later versions of Access would not
support partial replication.
I would seriously consider using VB Dot Net to build a new User Interface
and use Datasets to retrieve and update the data, you can serialise the data
into XML files on the Users PCs. You then do not need to license Access on
those PCs.
The downside of this approach is the development time but the solution is
intrinsically more robust.
Doug
"John" <Jo**@nospam.infovis.co.uk> wrote in message
news:ue**************@TK2MSFTNGP09.phx.gbl...
Hi
We have an access app (both front & back ends are in access) that runs
over win server networks. There are now more and more users who would like to
take away a copy of app with them, work offline, and when they come back
expect the client copy to sync (both ways) with the server copy. Seems
like a reasonable requirement. The question is; what do I need to do to make
this happen? Do I need to switch the backend to sql server? Front end to vb or
something like that? Anything else? How do other people do this?
Thanks
Regards