I'm developing an application for DB2 Everywhere on the palm (OS v3.1.1),
using CodeWarrior Release 6 with all patches and upgrades and POSE 3.0a8
(and a7 before it). We're almost done but recently I've noticed that some of
our DB2 tables become corrupted whenever we reset the emulator or the actual
PalmIIIe device.
I'm not just talking a few misplace characters. The tables become so garbled
that even going to Info/Delete in the Application Launcher or ANYTHING that
would access those tables, even to just see if they exist, causes an
"Invalid Handle" error in "MemoryMgrNew.c, Line 4128". The error is the same
regardless of the application that tries to access the table. Only certain
tables are affected. All the others come through unscathed.
Also , initially, I thought it was my application that was corrupting the
tables but I realised that in some of the saved emulator sessions my program
hadn't even been introduced yet. The same thing applies to the device.
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.
Anyone have any idea what happens during a reset that could cause this
problem?
Deadlines loom....
Thanx in Advance..
Dale Stephenson
TinCorps. Ltd.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
