> 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...
Unfortunately its EveryWhere.... we should be switching to Everyplace soon
but our local IBM is , how shall we say, deficient.
> 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.
No this happens w/o my app even being on the palm/emulator. But once its
reset (whether thru the emulator menu option or soft reset button on device)
the tables become corrupt.
> 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.
Nope doesn't seem to be.
>
> 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.
Ok will do .. wouldn't happen to have the direct URL for the forum would
you? : )
Thanks for the help though.
Dale Stephenson
[EMAIL PROTECTED]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
