Not true, the name must be unique regardless of the Type or creator ID
(residing on the same card and since current Palms only have one card, the
name must be unique to the unit)
-----Original Message-----
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: Palm Developer Forum <[EMAIL PROTECTED]>
Date: Wednesday, April 05, 2000 8:38 PM
Subject: Re: Database name uniqueness
>
>
>You can have another database same name with different TYPE.
>
>-Elizabeth
>
>
>
>
>[EMAIL PROTECTED] on 04/05/2000 03:47:59 PM
>
>Please respond to [EMAIL PROTECTED]
>
>To: [EMAIL PROTECTED]
>cc:
>Subject: Database name uniqueness
>
>
>
>
>The documentation for DmCreateDatabase() says that only one database with a
>specified name can exist (on a specific "card," but there's only one card).
>This means that even though applications must register their creator IDs to
>prevent conflicts, they can still conflict if they create databases with
the
>same name. Is that correct? Is there a standard naming convention to
avoid
>this?
>
>The documentation also recommends calling DmSetDatabaseInfo immediately
>after DmCreateDatabase to set the database version number, and there are
>other API functions (e.g. DmGetNextDatabaseByTypeCreator) which deal with
>the presence of several databases with the same type and creator but
>different version numbers. It looks like the intention here is that if I
>want to create a new version of my database, I also have to rename it. Is
>that right? Is there a standard usage model for database version numbers?
>
>
>
>
>
>
>--
>For information on using the Palm Developer Forums, or to unsubscribe,
please
>see http://www.palm.com/devzone/mailinglists.html
>
>
>
>
>
>
>
>
>--
>For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
