What I originally said IS a way to create a database, then convert it
to read only. It seems simply that THAT isn't what you need ;)
In any case, the creator thing explained by Richard is one way; the
other is to simple INSTALL the app you need and don't DELETE the old
app first... that way, the install conduit will OVERWRITE your
editing version of the APP with the non-editing version...
Alan Pinstein
Synergy Solutions, Inc.
http://www.synsolutions.com
1-800-210-5293
> My main problem here isn't really the creation of a read-only
>database, it's the question of how to add data and *then* have it be
>read-only. It seems like some programs can be deleted and have their
>database remain, but I haven't found any way to do this with mine. When I
>try to replace my editing version of the executable program with a
>non-editing version, the database always gets removed in the process. So
>how do I go about adding data to a database that will be accessed in a
>read-only fashion?
>
> Michael
>
>From Alan:
> >There is a db header attribute for readOnly. This prevents the DB
> >from being opened in dmModeReadWrite. You can programatically set
> >this bit by using the Dm[Get | Set]DatabaseInfo() calls.
>
> >***** Important note *****
> >You CANNOT successfully beam databases with the readONly bit set. We
> >ran into this problem while writing a beaming application. a quick
> >look at the sources and we realized that this is a due to a bug in
> >the Exchange Manager in the way it handles databases received with
> >ExgDBWrite(). I have sent a bug report in, so maybe in a future OS it
> >will be (has been?) fixed.
>
> >> This may be a silly question, but how do I go about creating a
>database
> >>that is readable, but not editable by a palm app (like a dictionary or
> >>online manual program)? I'd like to first use it to create the database,
> >>then modify the source code so that the app only reads, then recompile.
> >> However, to load the new version of the app, I have to delete the old
> >>version, and this deletes the database. Any tips on how to get around
> >>this?
> >>
> >> Michael
