> -----Original Message-----
> From: Michael McFarland [mailto:[EMAIL PROTECTED]]
>
>
> 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.
2) When deleting an application, all databases that share the
same creator ID are removed.
2) Apps can open, read & write to -any- database, even those
which have different creator IDs.
Putting 2 & 2 together we get this idea: give your "db initializer"
app a different creator ID than that used by the database it creates.
(The database can, and probably shoud, use the same creator ID that
the "read only" version has.)
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
