Disconnected Client Data Store

[John Wright]

What are some good stragegies for writting a disconnected client store. I
was looking at MSMQ, Serialization and possible SQL Server Express, but I am
open to any suggestions.

I have to scenerios.

1. I have a client/server application that needs to be connected as much as
possible. I plan on caching the lookup tables on the local machines and
running a thread every so often to check for differences. These tables to
not change much. We have an Oracle 10g rev 2 database and we are looking at
the Oracle client to receive notifications when these tables are updated and
make the changes. If the network goes off line (I have code to detect this)
I want to be able to save the current data they have saved, then stop the
program since I cannot retrieve data for the next part. However, I don't
want to loose the data they currently have. Once the network comes online,
I would like to pick up the saved data and pass it to the database.

2. I have a smart client application that needs to run independantly. If
the connection to the server is down, they people can still enter shipping
tickets and when the network comes back up, it will flush these requests to
the central server.
Any code or articles would be great.

John Wright

[Cor Ligthert [MVP]]

John,

You mean something as that you first write an
XML dataset to disk with the diffgram method.

http://msdn.microsoft.com/library/de...classtopic.asp

I can now write a long text but I assume that you understand it now
yourself, if not then reply.

Be aware that this can give errors (already processed rows) and probably you
have therefore to use the method where the errors are written in the
datarows rowerrors

Continue update on error
http://msdn.microsoft.com/library/de...errortopic.asp

rowerrors
http://msdn.microsoft.com/library/de...errortopic.asp

I hope this helps,

Cor
"John Wright" <ri**********@notmail.com> schreef in bericht
news:%2****************@TK2MSFTNGP03.phx.gbl...

What are some good stragegies for writting a disconnected client store. I
was looking at MSMQ, Serialization and possible SQL Server Express, but I
am open to any suggestions.

I have to scenerios.

1. I have a client/server application that needs to be connected as much
as possible. I plan on caching the lookup tables on the local machines
and running a thread every so often to check for differences. These
tables to not change much. We have an Oracle 10g rev 2 database and we
are looking at the Oracle client to receive notifications when these
tables are updated and make the changes. If the network goes off line (I
have code to detect this) I want to be able to save the current data they
have saved, then stop the program since I cannot retrieve data for the
next part. However, I don't want to loose the data they currently have.
Once the network comes online, I would like to pick up the saved data and
pass it to the database.

2. I have a smart client application that needs to run independantly. If
the connection to the server is down, they people can still enter shipping
tickets and when the network comes back up, it will flush these requests
to the central server.
Any code or articles would be great.

John Wright