J
Jason Shohet
I have an asp.net app, and suddenly, I lose connection to the web server.
I'd like a way -- if the update doesn't go thru, to 'cache' the changes to
the dataset.
Then the next time the user hits update, and the connection is restored, it
updates the db.
This applies for a WindowsCE device where the user is moving around, and may
not be able to connect for a few minutes at a time, but he/she is still
making changes to the app. I don't need for them to be able to retrieve
from the db, its enough that they can do updates, deletes etc on a
recordset stored on the device somewhere, and then when it connects again to
the web server, it does the updates / deletes etc.
Is this a dream or is there actually some way to do this.
I've been asking on the mobile newsgroup but not that much available there.
TY --- Jason Shohet
I'd like a way -- if the update doesn't go thru, to 'cache' the changes to
the dataset.
Then the next time the user hits update, and the connection is restored, it
updates the db.
This applies for a WindowsCE device where the user is moving around, and may
not be able to connect for a few minutes at a time, but he/she is still
making changes to the app. I don't need for them to be able to retrieve
from the db, its enough that they can do updates, deletes etc on a
recordset stored on the device somewhere, and then when it connects again to
the web server, it does the updates / deletes etc.
Is this a dream or is there actually some way to do this.
I've been asking on the mobile newsgroup but not that much available there.
TY --- Jason Shohet