Here's the deal:
(view1 is a view used in view2)
If I open/requery view2 which based, in part, on view1 everything is fine IF view1 was populated directly from it's underlying data (either used without the NODATA clause or requeried.
If I have populated view1 programatically from, let's say, a multi-select list on a form (this view1 is still a view based on a real table but was opened with the NODATA clause) then attempted to use or requery view2, view2 will not get popultated with any data.
So it appears to me that view2 will not work unless view1 has data in it directly pulled from it's underlying table.
This has been forcing me to use standard SQL Cursors for my reporting, which I don't mind, but I'd like to keep to the framework ideals. Does anyone have a suggestion? The data in view1 is usually the Id of it's underlying table.
Thanks in advance,
Gil Munk
"If a nation expects to be ignorant and free, it expects what never was and never will be." - Thomas Jefferson