Now, I noticed that the database are stored under a PALM_DM directory in the volume, and have filenames based on the Database name. Further, I noticed that the names are kind of encoded and does not have a .PDB extension.
I developed a code to enumerate all the files in the PALM_DM directory and identify the filename of the PDB I wanted to open. After it has located the file, it will try to open the file and determine the database type and creator. Now, VFSFileOpen works on the file, but when I do a VFSFileDBInfo (of course after the VFSFileOpen), it returns an error, vfsErrBadData.
I read from the documentation that I can use the VFS Manager functions to the files in the storage heap volume. I don't know what could be wrong -- if the volume is just like any other VFS compatible volume.
I speculate that VFSFileDbInfo expects a big-endian database, while the database files in the storage heap volume are stored as little-endian (native-ARM routines), making VFSFileDbInfo fail. What do you think?
Anyway, I hope someone can help me with this.
Thanks!
Mark
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
