A customer informed me that my conduit was causing his Palm to crash when it
attempted to update a database (which it does by deleting the existing DB
and then creating a new version). After some unsuccessful attempts to find
the problem, I told him to use the option of creating the database on the PC
as a .PDB file and installing it with Hotsync. It crashed again. Finally, I
told him to just delete the entire application and reinstall from scratch.
Attempting to delete the app from the launcher also crashed the Palm, and
the app would not go away (BTW, the app continued to work OK during all of
this).
Knowing that he had a Palm IIIxe, I then thought that it could be the DRAM
problem that had corrupted something and maybe a hard reset would be
necessary. I suggested that he go to the Palm site and get the DRAM test
program. When I next heard from him, everything was OK again. His unit had
passed the DRAM test, but while he was on the site he noticed the 3.5.2
update, downloaded it and installed it. Problem fixed! My conduit now works
again, and the database can be deleted and re-created.
So, this really makes me wonder what was fixed in 3.5.2. Does anyone know
what problem in the original 3.5 could have caused such a serious-appearing
problem with deleting my database? Anyone else ever see this kind of
problem?
Doug Gordon
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
