It seems that the term "cascading" has not been differently understood by the ASP.Net community.
Most people writing about "cascading" makes you feel like is something that only has to do with "filtering" and nothing else.
I have been trying to understand for almost one year what is all about behind the scenes to make "cascading" work, and it is true that passing values of variables has been a gigantic issue but "not the issue" because when you can do that (passing values) you realize that such things is not simply enough and IT IS NOT THE ASNSWER YOU ARE LOOKING FOR.
I have found many ways of passing these values. I have worked on different approaches and some of them seems to work better than other, more efficient, with less code, with less downgrade in performance, with less calls to the database, etc.
But the "real issue" of cascading is not that, so I'm wondering: How can you make (call it "customize") that the REFERENTIAL INTEGRITY among all different FKs could be maintainded at "DATA LEVEL"?
What I am trying to say is ... ...
Ok! ... Let's suppose you already know how to pass the values of some pre-customized filters to your Insert.aspx page (or any other page) and the dropdowwnlists are shown ok! ... ... ... BUT ... ... ...
View Complete Post