Dennis (DevExpress Support)
04.27.2009
Show all comments
-
Are there any plans to do this, or has this been consigned to the now invisible "Accepted"/"TBD" pile of items ?
-
Hi Chris,
I still want to create an example (I cannot provide any ETA, though) that demonstrates how a similar problem is handled in our internal XAF application, e.g., when an operator wants to open a record that is already opened and processed by another one. In particular, we display a warning message that asks whether an operator still wants to work with a locked record for viewing. I opted for this scenario, because I also saw that other customers implemented something similar in their apps. Please let me know if you are interested in this scenario or if your requirements are different.
-
Hi Dennis
Thanks for the response.
I did look at and play with the "RecordLocking" example that you posted in another thread. This does work in a simple scenario i.e. a lock depth / lock dependency of 1.
My use case is a Sales Order with associated Sales Order Lines. I'm currently trying to see if the example can be extended to work in this scenario.
Chris
-
Thank you for the feedback, Chris.
-
*** This is not a "Solution" but I can't comment!!!
@Dennis: an example would be highly appreciated.
@Chris: what "RecordLocking" example are you talking about? Can you provide a link?
Thanks.
-
@Robert - Also not a solution - http://www.devexpress.com/Support/Center/p/Q203772.aspx
-
Thanks, Chris.
You must
log in
or
register
to leave comments
Is your intention to post an answer to your own question?
- If so, then proceed.
- If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
- If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.
Facebook
Twitter
Google+