>For this application, stay away from the File Streaming API. It uses
>record databases
>as it's underlying representation. All the record sizes are fixed at 1024
>bytes (not
>officially stated anywhere, subject to change, yadayada).
Huh? Why would this be relevant? It is like saying "don't use that hard
drive; it uses sectors of 2048 bytes each; that's no good for your app"...
who cares what the physical media's attributes are, if it doesn't affect
the higher-level view of the data?
The application using the API doesn't see any of that layer; it just gets
data from any offset, or in a streaming fashion.
It might well be that the file streaming API isn't what they want, if the
goal is to have the data be resource databases. But the block size
shouldn't be relevant as far as I can tell.
(And to rename databases, of any kind, use DmSetDatabaseInfo.)
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
