rubbernilly
Programmer
Apologies if this has been asked elsewhere. My search turned up no direct results.
I have a form with three subforms. The subforms are stacked vertically, but do not touch/overlap. They are the width of the main report, and they are 0" height. I want them to expand if there is data in that subreport dataset. The first 2 expand just fine, but the third will not.
I have confirmed all of the settings (can grow, etc.), and I know that the third report should be growing because if I reorder my stack of subreports (putting #3 between #1 and #2), then it is still the top 2 subreports that grow, and the third (which is now #2), will not. It seems Access will only "Grow" the first two.
I have seen discussions this as a sort of known bug, but I haven't seen a workaround besides embedding (in this case) my subreport #3 in subreport #2, so that Access is tricked into thinking it only has 2 subreports, and will expand things properly. I also understand there is a "VerticalAnchor" property in newer versions of Access which might or might not help.
Is there not a clean fix for this?
I have Access 2007, with Office 2007 SP2.
I have a form with three subforms. The subforms are stacked vertically, but do not touch/overlap. They are the width of the main report, and they are 0" height. I want them to expand if there is data in that subreport dataset. The first 2 expand just fine, but the third will not.
I have confirmed all of the settings (can grow, etc.), and I know that the third report should be growing because if I reorder my stack of subreports (putting #3 between #1 and #2), then it is still the top 2 subreports that grow, and the third (which is now #2), will not. It seems Access will only "Grow" the first two.
I have seen discussions this as a sort of known bug, but I haven't seen a workaround besides embedding (in this case) my subreport #3 in subreport #2, so that Access is tricked into thinking it only has 2 subreports, and will expand things properly. I also understand there is a "VerticalAnchor" property in newer versions of Access which might or might not help.
Is there not a clean fix for this?
I have Access 2007, with Office 2007 SP2.