Sure, NVFS layer adds new errors. So what was true at the time the manual
was written (err code is 0|dmErrCantFind), does not hold true anymore.
Be careful if you get vfsErrorClass errors. Something goes wrong in the NVFS
layer then.
With best regards,
Jan Slodicka
Resco, Palm Division
----- Original Message -----
From: "Mike" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[email protected]>
Sent: Saturday, August 05, 2006 12:52 AM
Subject: DmGetLastErr
> On the newer Palms (Treo 650, T5, etc) DmGetLastErr isn't working as
expected.
>
> dbID = DmFindDatabase (0,DBName); // DBName doesn't exsist in this case
>
> if(dbID)
> { // handle the exsisting db
> }
> else
> {// FindDB failed, find out why
> Err er1 = DmGetLastErr();
>
> if(er1 == dmErrCantFind)
> {// create
> }
> }
>
> In the code above, er1 is zero, not dmErrCantFind . According to the docs,
you should be able to call DmGetLastErr to see why DmFindDatabase failed.
Are there any known issues with this?
>
> This code works on older Palms.
>
> TIA,
> Mike
>
> --
> For information on using the PalmSource Developer Forums, or to
unsubscribe, please see http://www.palmos.com/dev/support/forums/
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
