What is best practice for a scenario where you may have an object, that may have a different parent object depending on the form it is used in? For example, I have an object called parts. Parts can be called in my application to create a proposal (kind of sales order) of which I presently have 4 different types, they may also be used in invoicing, they may also be used in Jobs, where again parts may be used for maintenance purposes.

thanks in advance

Geoff Hirst

When doing this, you can dynamically change the relationship between the parent BO and the child BO.  This does, however, have to be done in code and will require that you set the value of the child field when a new record is created.  But once that is done, all of the same functionality as using the ParentRelationship logic will still work, including the automatic update of child FK values if the parent is a new record, etc.

Thanks for that chap, just what I needed.

Just another thing, should the naivgated event fire after a seektoprimarykey? Doesn't seem to be doing for me.

thanks for the help.

G.

If you do want to update the UI, however, you can use the NavigateToPrimaryKey, which will fire the Navigated event upon completion .