Re: Non-skipping IDs with Master-Detail


Hi Vitali,

Please read my new post with subject: In-Memory Dataset

Thanks!


"Vitali Kalinin" <vitkalinin@xxxxxxxxx> wrote:
>
>"Michelle Brennan" <mibi222@xxxxxxxxxxx> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
>ÓÌÅÄÕÀÝÅÅ: news:435cf387$1@xxxxxxxxxxxxxxxxxxxxxxxxx
>>
>> Thanks Vitali!
>>
>> How do I make OrderID of type GUID? I saw some sample code but
>> I haven't figured out how it works. It seems like just a large
>> field to hold unique values. How does this help in keeping
>> Master-Detail relationship? Isn't it enough to just use normal
>> integer fields (not IDENTITY) for IDs and prevent it from
>> duplicating?
>GUID could be generated on the client side and granted to be unique, so you
>will know pk value for master record before Post or BatchUpdate.
>
>

.