My test databases have 10000 to 20000 records. My program "gets" every
record and locks it (then releases all of them and closes the database
on quit). I bet that if I just got one at a time and released it, the
databases wouldn't be disappearing. But, that's not an option (if I
want decent performance) because I'm doing lots of calculations and
sorting using data from every record.
This app has been out for over a year and works on devices back to the
Palm III and OS 3.0. Now it's having all these problems on NVFS
devices: busy records after a reset and disappearing databases.
For now, I'm just telling my customers that it's a bug in Palm OS. But,
that answer is not satisfying to anyone - especially when these devices
have been around for awhile now and Palm doesn't seem to be doing
anything about it.
If anyone has any other ideas, I'm up for trying.
Terry
On Aug 12, 2006, at 7:01 PM, Terry wrote:
Thanks for the suggestion. I did exactly what you wrote. The database
still disappears. I tried it three times. The error returned from
DmCloseDatabase is zero.
[...]
On Aug 12, 2006, at 4:58 PM, Dmitry Grinberg wrote:
try this:
-make sure your app CLOSES the database whenit exits
-download MemInfo.
-run your app and modify some records
-open memInfo and flush DbCache usnig MemFill Method
-turn device off for 30 seconds
-reset [while device is still off]
see if database is gone now
On 8/12/06, Terry <[EMAIL PROTECTED]> wrote:
I've been testing my program with different size databases on a Palm
TX. Some of the databases disappear every time after a reset. Other
databases never disappear no matter what I do. It seems to only occur
with databases around 4MB to 7MB. Larger ones, or smaller ones never
disappear. The number of records does not seem to matter, just the
overall size.
For the database to disappear, some records must have been modified
first. If I just hotsync the database, then reset, it's still there.
If
my app only reads from the database, it's still there after a reset.
My program does not have to be running during the reset. It only had
to
have written to some records beforehand.
Before the reset, the databases works fine. I can read and write,
quit,
run it again, and it's always there. The simulator reports no errors.
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
