From: Dale Stephenson [mailto:[EMAIL PROTECTED]]
> I'm developing an application for DB2 Everywhere on the palm
Do you really mean the obsolete DB2 EveryWHERE version 1.2, or the current
DB2 EveryPLACE version 7.1.x? I'll assume the latter below...
> The important/interesting point here is : the tables are perfectly fine
> initially. All applications run and use them w/o problems. But the minute
> the device/emulator is reset for whatever reason they become corrupted.
Do you mean the reset happens when your app is running and using DB2e?
There is a known bug in that scenario. If your app aborts with a cursor
open, then DB2e leaves some temp tables around. Then the next time you
connect to DB2e, it tries to erase them, but its cleanup logic is buggy and
crashes. This is easy to work around by writing your own code to do the
cleanup.
> Anyone have any idea what happens during a reset that could cause this
No, if it's not the scenario described above, then it's weird. Test with a
no-notify reset (hold down the scroll-up button) and see if it still
happens.
Also make sure to use the latest DB2e version, currently 7.1.1. And
consider posting problems on IBM's DB2e web forum in addition to here.
-slj-
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
