>It means, This is the failure of VFP.
>
>I am amazing FPD26 could handle such task then why VFP not.

Conceptually there is not much difference between FP 2.6 FRX designer / engine and VFP6-8
They both have certain conceptual limitations. However back in 2.6 you could fill up those gaps by
reporting programmaticaly via ?/?? commands, whereas in VFP versions 6-9 those commands are no longer sufficient
taking into consideration modern reporting requirements with graphics, fancy fonts etc.

This is one of the reasons why RS was made. If FRX does not cut, you can always create ANY kind of report
programmatically. RS methods .LF() and .LW() are made to cover ?/?? reporting style;

.lf() &&advances one row
.lw(25,'something')  &&write in current line.

Amount of that old style reporting code can be drastically reduced by using more advanced scenario with form objects;
You design your bands visually (as form containers) and then you 'drive them' directly from within code.

.Advance(nPixels) &&advance +/- N pixels up/down the page
.FlashContainer(thisform.myDetailBand)   &&Render form container at current page position

This way you get best of both worlds; Flexibility and precision of coded reporting and ease of visual content design.

Or to put it in context of your report, you design first half of the page as one container and second part as another.
Then call them accordingly in some loop

select table1
scan
  .FlashContainer(thisform.Container1)
  select table2  &&related by some key
  .FlashContainer(thisform.Container2)
  .Eject()
endscan

HTH
Sergio