J
Jason Shohet
We have people that do mailing runs around NYC, and need to be able to
retrieve and input data from our central Oracle database, on a mobile (I
guess lets assume CE) device. They have records of their runs, and then
check off fields when they are done.
What happens when the device can't connect to the internet? Can they input
data, and then have it cached, and then synch it back up with IIS and our
Oracle database when the device comes back online? How would this work.
If the answer is no, it seems I'm totally sc**wed.
Would the 2nd best thing be to have some local db on the device (ie, Access,
Sybase SQL Anywhere? suggestions?), and a local WindowsCE app on the device
connects to our main Oracle db, pulls down records for the run into a
dataset, and saves that dataset to Access on the device. Then the user does
his run, updates the local Access db, and then when he comes back into the
office, the application takes the information from the local db on the
device, and updates the main records in the Oracle database. This seems a
horrible way to go....
Thanks for any suggestions
Jason Shohet
retrieve and input data from our central Oracle database, on a mobile (I
guess lets assume CE) device. They have records of their runs, and then
check off fields when they are done.
What happens when the device can't connect to the internet? Can they input
data, and then have it cached, and then synch it back up with IIS and our
Oracle database when the device comes back online? How would this work.
If the answer is no, it seems I'm totally sc**wed.
Would the 2nd best thing be to have some local db on the device (ie, Access,
Sybase SQL Anywhere? suggestions?), and a local WindowsCE app on the device
connects to our main Oracle db, pulls down records for the run into a
dataset, and saves that dataset to Access on the device. Then the user does
his run, updates the local Access db, and then when he comes back into the
office, the application takes the information from the local db on the
device, and updates the main records in the Oracle database. This seems a
horrible way to go....
Thanks for any suggestions
Jason Shohet