|
Home > Archive > MS Access Multiuser > April 2005 > Offline use
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| 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
| |
| Van T. Dinh 2005-04-21, 8:25 pm |
| Read up and read a lot (Access Help, Access books, Microsoft Web sites,
other sources ...) on Replication and try it on a *copy* of the database
first before trying to implement on the production database.
--
HTH
Van T. Dinh
MVP (Access)
"John" <John@nospam.infovis.co.uk> wrote in message
news:et4hGBtRFHA.904@tk2msftngp13.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
>
>
| |
|
| I tried that but find it unreliable. Ideally I do not want to mess with the
backend db where the data is. That is why I am asking the sql server
question which I presume supports syncing natively and presumably reliably.
Thanks
Regards
"Van T. Dinh" <VanThien.Dinh@discussions.microsoft.com> wrote in message
news:%23nX$CMtRFHA.1096@tk2msftngp13.phx.gbl...
> Read up and read a lot (Access Help, Access books, Microsoft Web sites,
> other sources ...) on Replication and try it on a *copy* of the database
> first before trying to implement on the production database.
>
> --
> HTH
> Van T. Dinh
> MVP (Access)
>
>
>
> "John" <John@nospam.infovis.co.uk> wrote in message
> news:et4hGBtRFHA.904@tk2msftngp13.phx.gbl...
> over
> like
> this
or[color=darkred]
>
>
| |
| Van T. Dinh 2005-04-21, 8:25 pm |
| Yes, SQL Server supports replication also.
Check the SQL Server B.O.L. on Replication.
After you read the B.O.L., I would suggest checking the SQL Newsgroups also
to see potential problems of what you are trying to do.
--
HTH
Van T. Dinh
MVP (Access)
"John" <John@nospam.infovis.co.uk> wrote in message
news:eNIewjtRFHA.3732@tk2msftngp13.phx.gbl...
> I tried that but find it unreliable. Ideally I do not want to mess with
the
> backend db where the data is. That is why I am asking the sql server
> question which I presume supports syncing natively and presumably
reliably.
>
> Thanks
>
> Regards
>
>
| |
|
| Hi John,
yes in SQL you can do replication, the type of replication you are
looking for is merge replication within SQL, it also is not perfect and
would require modification of your data structures.
Regards
Alex
|
|
|
|
|