We have a SQL database (BE) with MS_Access (FE) that works well (~80 users).

New requirement - we need to take this application, put it on 12 laptops so
the data can be collected at remote sites - (sites without a connection to
the internet, not even wireless connections.)

What is the best way to look into what it takes to put an application on
laptops so data can be collected and then transfered(?) to the central SQL
database?

Thanks,

Regards

A good search term for this would be "occasionally connected applications"

Tom Dacon
Dacon Software Consulting

"rg" <rg01@NoReplyPlease.NRP> wrote in message
news:ue66b4PFJHA.4948@TK2MSFTNGP04.phx.gbl...
> We have a SQL database (BE) with MS_Access (FE) that works well (~80
> users).
>
> New requirement - we need to take this application, put it on 12 laptops
> so the data can be collected at remote sites - (sites without a connection
> to the internet, not even wireless connections.)
>
> What is the best way to look into what it takes to put an application on
> laptops so data can be collected and then transfered(?) to the central SQL
> database?
>
> Thanks,
>
> Regards
>

Merge replication is the top thing that comes to my mind. Perhaps some
other form of replication.

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"rg" <rg01@NoReplyPlease.NRP> wrote in message
news:ue66b4PFJHA.4948@TK2MSFTNGP04.phx.gbl...
> We have a SQL database (BE) with MS_Access (FE) that works well (~80
> users).
>
> New requirement - we need to take this application, put it on 12 laptops
> so the data can be collected at remote sites - (sites without a connection
> to the internet, not even wireless connections.)
>
> What is the best way to look into what it takes to put an application on
> laptops so data can be collected and then transfered(?) to the central SQL
> database?
>
> Thanks,
>
> Regards
>