Object that could potentially have multiple parents.


Author
Message
Geoff Hirst
Geoff Hirst
StrataFrame User (221 reputation)StrataFrame User (221 reputation)StrataFrame User (221 reputation)StrataFrame User (221 reputation)StrataFrame User (221 reputation)StrataFrame User (221 reputation)StrataFrame User (221 reputation)StrataFrame User (221 reputation)StrataFrame User (221 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
Dustin Taylor
Dustin Taylor
StrataFrame Team Member (660 reputation)
Group: StrataFrame Users
Posts: 364, Visits: 771
The Navigated event won't fire after a seektoprimary key since a seek doesn't update the bound controls (which is the difference between "navigate" and "move".) The seek method will return True or False based on whether it is successfull, so you could test on that and fire off whatever code you needed to in the same code block.

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

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