It's not a question of improving the function, rather of completing
the database. ErrorCodes (http://prc-tools.sourceforge.net/
errorcodes.html) does this.
However, this only gets you the PalmSource (Access) error codes. It
doesn't give you vendor error codes, which now includes Palm (nee
palmOne). And Palm reuses the same error code for different
libraries with different meanings.
On Feb 27, 2008, at 8:34 AM, Kelly Leal wrote:
Can someone tell me if the SysErrString function has been improved
in Palm OS 5? Can it handle correctly all the errors?
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/