My application needs a large (> 500 KB) binary data set in order to run. Once running, it needs very fast random access to this data. It is not an issue to break the data into about 100 records < 64K... It seems the standard way is to develop a conduit that writes this out as a database. But due to the following issues I was wondering if any of you has a better suggestion? (For example, could I mimic the format of a resource file and just have the file uploaded by the default installed and somehow find it on the palm?) Thanks! - Jeff ISSUES: ACCESS SPEED - I don't know a fast way to do random access through a lot of DB records other than to make the DB non-movable. As long as all the DB records are created in contiguous memory, this is not a bad solution, but if NOT - this would horribly fragment memory! DEVELOPMENT - I'd have to write a special hot sync conduit (and Palm data verifier) before my actual application, and it might get complicated because I want to update the data resource separately from the program resource - I definately wouldn't want Codewarrior to try to recopy the resource file each time I do a rebuild. And I'd have to work with two different projects all the time. RECORD ORDER - it doesn't seem like you can guarantee the record order with the API - any better solution to this than to run a program on the Palm that builds an index database of which records have what IDs? Any ideas? -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
