Object that could potentially have multiple parents.


Author
Message
Geoff Hirst
Geoff Hirst
StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)
Group: Forum Members
Posts: 123, Visits: 3.5K
Guys,

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

Reply
Geoff Hirst
Geoff Hirst
StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)StrataFrame User (323 reputation)
Group: Forum Members
Posts: 123, Visits: 3.5K
Trent,

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.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search