Aaron Ardiri wrote:
> On Mon, 31 May 1999, Keith Wolcott wrote:
> > Aaron,
> >
> > All databases must have unique names. Thus, it is also a good idea to
> > have some part of your database name be something unique to your
> > program. Otherwise you could accidentally trash someone else's
> > database. There was a long thread some time ago about the merits of
> > either prefixing or appending your creator ID to each associated
> > database.
>
> understood!.
>
> however it is kindof strange. :) i guess it is because of
> HotSync :) you dont get to access the creatorID from the file
> name it generates.
>
> it is a pretty bad restriction! i guess from a developers
> point of view, it can always be hidden from the "user" with
> smart coding.
>
> ie: when creating, prefix the creator ID,
> when accessing, remove the creator ID from the front.
>
> it should be invisible to the user.
>
> small about of "extra" coding :P
That is correct. That is what I do with one of my programs. I prefix a
string, but strip it for the user view of it. I chose to prefix it, since
when sorted in the desktop backup folder, databases for my program all apear
together.
>
>
> PS: How is Jane going with LodeRunner? passed level 70? :))
>
She has not had time yet, but says that she will beat your score.
Keith Wolcott
