Paul,

I just looked at FRX2WORD over the weekend after having trouble in my tool sometimes locating objects in the correct band. I believe the problem in FRX2WORD is that the number that is used for the BAND HEIGHT 1979.16666666 is only 19 pixels high at 96 DPI rather than the 20 pixels high of the actual GROUP BAND object used in the designer which is an equivilant to 2083.3333333. What happens then is after you start adding a bunch of bands to a report it starts picking up objects and locating them in the incorrect Band. So this may cause your overlap problems just as a guess. I actually spent about 3 hours yesterday analyzing the Actual Height of objects stored in BANDS of varying height by creating BAND HEIGHTS in 0.10 and 0.001 inch increments in the VFP Report Designer and then studying the FRX output and found that there is a 4.167 unit difference variance between each 0.10 inch increment in size for every quarter inch. Then the same applies per 0.01 inches variance as well. What a PITA!

Here is some example BAND HEIGHTS and OBJECT HEIGHTS in FRUs:

BAND OBJECT
HEIGHTS HEIGHTS
5000 5000.000
5100 5000.000
5200 5104.167
5300 5208.333
5400 5312.500
5500 5416.667
5600 5520.833
5700 5625.000
5800 5729.167
5900 5833.333
6000 5937.500
6100 6041.667
6200 6145.833
6300 6250.000
6400 6354.167
6500 6458.333
6600 6562.500
6700 6666.667
6800 6770.833
6900 6875.000
7000 6979.167
7100 7083.333
7200 7187.500
7300 7291.667
7400 7395.833
7500 7500.000

Now all we have to do is right a function to emulate that! <bg>

Anyway, FRX2WORD works fine until you have so many bands that the adjustment for the band height starts creeping into previous bands. Then you have a problem.