My application has what may be an atypical configuration, in that it's using a tabbed gridlinker where I have a parent grid with 3 reference number fields that I use to link to 3 instances of the same child grid (each defined with a unique alias). Each record in the parent grid may have anywhere from 0-3 reference numbers populated in the appropriate fields. In cases where reference number(s) exist for a given record in the parent grid, there is only a maximum of 1 record linked to it in each child grid instance.
I realize that the way something like this would typically be handled would be by simply basing a grid upon a view that joins the 2 tables behind each of the grids, and that tabbed gridlinkers are typically used in applications which link 1:Many records. But, given the similarities between the 2 tables and the data contained within them, it seemed a less confusing approach to use a tabbed gridlinker, especially because of the way in which the tables' data are displayed as separate logical entities.
This approach has worked rather well, with exception of some presentation issues that I'm trying to iron out. Specifically, seeing as how I have a maximum of 1 record in each child grid instance, I would like to hide a number of elements that are usually displayed, including the Search and Grid components and automatically display just the Details component right away. The problem here is that I cannot get the child grid to always show its Details component, even if I override this property. Given this, even removing the Search & Grid components from the tabbed gridlinker via Customize Page Layout doesn't do the trick, due to the fact that the Details component will not automatically display. In fact, I'm attempting to override several properties, and none of them seem to be taking, for whatever reason. These include:
tmpl.show_title = .f.
tmpl.DetailView.OnlyShowOnRequest = .f.
tmpl.DetailView.HideGridIfDetailViewIsVisible = .t.
tmpl.DetailView.HasTitle = .f.
Actually, typing this all out made me think to try this is regular grid, and it doesn't appear to take effect there, either. I've tried several combinations of the above settings with no luck. So, this would appear to be a more generic grid issue..? Is this a bug, or have a missed some prerequisite configuration needed to get this to work?
Regards,
Tarek
I realize that the way something like this would typically be handled would be by simply basing a grid upon a view that joins the 2 tables behind each of the grids, and that tabbed gridlinkers are typically used in applications which link 1:Many records. But, given the similarities between the 2 tables and the data contained within them, it seemed a less confusing approach to use a tabbed gridlinker, especially because of the way in which the tables' data are displayed as separate logical entities.
This approach has worked rather well, with exception of some presentation issues that I'm trying to iron out. Specifically, seeing as how I have a maximum of 1 record in each child grid instance, I would like to hide a number of elements that are usually displayed, including the Search and Grid components and automatically display just the Details component right away. The problem here is that I cannot get the child grid to always show its Details component, even if I override this property. Given this, even removing the Search & Grid components from the tabbed gridlinker via Customize Page Layout doesn't do the trick, due to the fact that the Details component will not automatically display. In fact, I'm attempting to override several properties, and none of them seem to be taking, for whatever reason. These include:
tmpl.show_title = .f.
tmpl.DetailView.OnlyShowOnRequest = .f.
tmpl.DetailView.HideGridIfDetailViewIsVisible = .t.
tmpl.DetailView.HasTitle = .f.
Actually, typing this all out made me think to try this is regular grid, and it doesn't appear to take effect there, either. I've tried several combinations of the above settings with no luck. So, this would appear to be a more generic grid issue..? Is this a bug, or have a missed some prerequisite configuration needed to get this to work?
Regards,
Tarek