VB.Net - Multiple Datasources

[Josh]

I'm looking for a little guidance, not necessarily code examples. Here's my
situation. I have written a web based application that rides on SQL Server.
Although it is web based and can be distributed to virtually anyone, the
client wanted additional "disconnected" abilities. As a result, I wrote a
VB.Net client application that uses a portion of the SQL Data, stored in
a local Access Database. Field employees enter data into the client application
for later insertion into the master database.

I'm curious as to a "best practice" for pushing the SQL data to the client
app for a full refresh of the local Access DB, at the same time pushing any
new entries on the client DB into the master SQL DB.

Any insight would be appreciated.

[Taiwo Ayedun]

To keep the data access code uniform I'd recommend using MSDE on the client.
When the SQL Server is available, you can send data in the local MSDE to SQL
Server via a web service (you can also compress the data).

Cheers,

Taiwo

"Josh" <joshplummer@computol.com> wrote in message
news:3e3ecadd$1@tnews.web.devx.com...
>
> I'm looking for a little guidance, not necessarily code examples. Here's
my
> situation. I have written a web based application that rides on SQL
Server.
> Although it is web based and can be distributed to virtually anyone, the
> client wanted additional "disconnected" abilities. As a result, I wrote a
> VB.Net client application that uses a portion of the SQL Data, stored in
> a local Access Database. Field employees enter data into the client
application
> for later insertion into the master database.
>
> I'm curious as to a "best practice" for pushing the SQL data to the client
> app for a full refresh of the local Access DB, at the same time pushing
any
> new entries on the client DB into the master SQL DB.
>
> Any insight would be appreciated.

[Kunle Odutola]

Taiwo Ayedun wrote:
> To keep the data access code uniform I'd recommend using MSDE on the
> client. When the SQL Server is available, you can send data in the
> local MSDE to SQL Server via a web service (you can also compress the
> data).

Depending on what the apps does and what editions of Windows it runs on, you
might also want to consider using the Message Queuing facility to send all
modification requests to the main server - app server not database. There is
then no need for two-way sync on the databases. Just an extract of the data
relevant to the guy in the field.

Kunle