>>For PK/FK we're using "pseudo" GUIDs (just alphanumerical). Should we use uniqueidentifier field in SQL Server for them?
>>How can we get new ID after insertion using this type of field?
>
>I don't know what does pseudo GUID is:) If you use strign form of GUIDs (36 characters, or 38 with {}) on VFP side that is transparently recognizable on SQL as a uniqueidentifier. Yes uniqueidentifier on SQL.
>
>It is the beauty of a GUID, you don't need to go and ask server what is my new ID? You create it and use it. Server learns the ID after you do:) No fixup necessary for parent-child-grandchild (and disconnected) scenarios.
>
>Cetin

Not sure what do you mean here. When we created a new parent record and want to insert a new child record in the child, what should we use for FK field?

In other words, if I start a transaction in SQL and I have SP InsertParentWithChildren how should I code it?

Thanks again.

Or are you saying that I need to set @NewID = NewID() and put it in both parent and child rather than omitting PK field in INSERT statement?