Re: Non-skipping IDs with Master-Detail
- From: "Vitali Kalinin" <vitkalinin@xxxxxxxxx>
- Date: Mon, 24 Oct 2005 18:36:41 +0300
"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.
.
- Follow-Ups:
- Re: Non-skipping IDs with Master-Detail
- From: Michelle Brennan
- Re: Non-skipping IDs with Master-Detail
- References:
- Non-skipping IDs with Master-Detail
- From: Michelle Brennan
- Re: Non-skipping IDs with Master-Detail
- From: Brian Bushay TeamB
- Re: Non-skipping IDs with Master-Detail
- From: Michelle Brennan
- Re: Non-skipping IDs with Master-Detail
- From: Vitali Kalinin
- Re: Non-skipping IDs with Master-Detail
- From: Michelle Brennan
- Non-skipping IDs with Master-Detail
- Prev by Date: Re: Non-skipping IDs with Master-Detail
- Next by Date: Re: Invalid Variant Type
- Previous by thread: Re: Non-skipping IDs with Master-Detail
- Next by thread: Re: Non-skipping IDs with Master-Detail
- Index(es):