Hmm... is it possible that the Unique ID for the new copy
is set only after the first Hotsync? I seem to recall that
hotsync was involved in unique record IDs somehow ... but
I thought that it was the Palm that assigned them and
records created on the PC didn't have unique IDs until
they were sync'd to the Palm ... so this seems backwards.
Do a sync and check the UniqueID of the new db again
and see if it has changed from 2C 00 00 00 to something
more reasonable.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
Shay wrote in message <33663@palm-dev-forum>...
>
>sounds correct BUT - when i take the PDB with Unique ID = 61 74 69 6F
(hex),
>and copy it to another place, the new one have an ID = 2C 00 00 00 (hex).
>
>i don't think it's correct, too many zeroes.
>
>if it will help, in the DataPrv.h it says :
>
>DWord uniqueIDSeed; // used to generate unique IDs.
> // Note that only the low order
> // 3 bytes of this is used (in
> // RecordEntryType.uniqueID).
> // We are keeping 4 bytes for
> // alignment purposes.
>
>shay
>
>
>
>"Richard M. Hartman" <[EMAIL PROTECTED]> wrote in message
>news:33617@palm-dev-forum...
>>
>>
>>
>> Shay wrote in message <33590@palm-dev-forum>...
>> >
>> >hi,
>> >i want to copy a PDB manually, so i succeed to do all the things except
>the
>> >field : uniqueIDSeed
>> >
>> >how can i READ this field ? so i could put it back in the
>DatabaseHdrType.
>> >
>>
>> I don't know for certain ... I am only making a rash assumption based
>> upon the name of the field ... but I have to assume that this is filled
in
>> by the OS in such a way as to be unique to each db. I mean ... if you
>> could copy it, it wouldn't be a unique ID would it?
>>
>> --
>> -Richard M. Hartman
>> [EMAIL PROTECTED]
>>
>> 186,000 mi/sec: not just a good idea, it's the LAW!
>>
>>
>>
>>
>>
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
