Second problem with SDTK. Filters. If you are using 2 BO that are bound with a SDTK and you filter one of them the second is filtered. Is there a reason for this? For my thought process is for lookups that rarely get update or automatically notified if DB changes then having a BO with a SDTK would work well and does. Up until one of those BO's are filtered for some reason and then All of the BO's are filtered. This obviously messes up a bunch of things.
Any ideas?
Richard
The best thing I could recommend here is to create a small sample that reproduces the issue you are describing versus going back and forth and we will take a look at it.
This is correct and by design. From the sound of it you may be overusing the shared data table. The shared data table is the internal data of the BO...this includes the DefaultView attached to that shared data table which is shared as well. Secondly, and I know that you have probably read this on other posts, but if you find yourself using a filter a lot, then you probably should be restructuring some of your code because this generally indicates that you are bringing back more data to the client side that may be necessary. Just a recommendation. This is something that we will cover in class and is something that I have been having a lot of conversations about lately. Filters are great when using under cetain conditions...and in moderation. But if this is a common design of your application you are in for a lot of frustrations and the larger the application grows (or the more data added from a larger client) the more problems you will encounter.