On Friday 14 September 2012 06:15:42 news.gmane.org wrote: > >> And during this (parent.query.active => child.query.active) activation > >> we should check that there's no such field so there's no need to > >> inform the user about that since one just deleted this field > >> intentionally :) > > > > What next? To give one's shoes a shine? > > Really, what user should do having this message displayed ? Which means > that the query on PARENT1FORM refuses to activate because some fields were > removed from its descendant on PARENT2FORM. But the descendant query > activates well.
But the field bindings of the lookup buffers are invalid and the application will crash at runtime. > Is it really as designed ? Yes. Martin ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
