Alternatives to the desire to do a programmatic hard reset to wipe the data:
1. Write a conduit to clear the applicable database
or
2. Add routines to clear the data after the results are beamed successfully.
okay, I thought of a legitimate application for a program that does a
hard reset that would be genuinely useful: In a fleet environment (e.g.
the company bought 20 of them for field service work or meter-reading of
some kind) and something like repair orders are beamed in at the
beginning of the day, then the results are beamed back to a server at
close of business. As each employee leaves the building he/she runs the
"Forget" program and leaves the palm device in a charging dock. The next
morning the dispatcher beams orders into the devices (as memos?) before
the field service people arrive, so all the devices are interchangeable;
no history to preserve.
It would be just as good or better to implement a "Forget" button in the
application that only wiped the local pdb clean, but I can just imagine
losing that argument with a middle manager (sigh. think I'll go read a
dilbert cartoon...)
why not just provide instructions on how to do a hard-reset? :) some
things are best NOT done in software *g*
--
Steve Jerrett
Systems Analyst
City of Columbia, MO
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
