This is a known bug, and is one of the reasons we produced the 3.5.2 update.
The bug existed in the source code all the way back to Palm OS 3.0, but we
were lucky. The compiler produced code that initialized the err variable to
zero. In Palm OS 3.5, we used a new version of the compiler, and we weren't
so lucky.
The bug causes ExgDBRead to return spurious errors when the database being
created has no records/resources. You could work around the bug by ignoring
the result, and checking whether the new database was successfully created
instead. But I don't recommend this approach. Better to ask your users to
install the 3.5.2 update. This update fixes another bug as well. Orphaned
chunks weren't getting cleaned up on reset.
--
Danny Epstein
OS Engineer, Palm Inc.
"Sören Henkel" <[EMAIL PROTECTED]> wrote in message
news:38328@palm-dev-forum...
> I've found that in OS 3.5.0 ExgDBRead() "sometimes" returns (non-existing)
error codes likes 0xD6BC, 0x85B6, 0x7152, 0x8818.
>
> That problem seems not to exist in former releases of PalmOS, nor in OS
3.5.2.
>
> Is this a known bug in 3.5.0?
> Is there a workaround other than installing the 3.5.2 update?
> Any other background information on that problem?
>
> Regards
>
> -Sören
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
