>>>>>In the following scenario, on a report, how can I make the location of Field02 relative to the end of Field01? These are footnotes if the helps clarify the issue.
>>>>>
>>>>>

>>>>>FIELD01XXXXXXXXXXXXXXXXXXXXXXXXXXX   FIELD02XXXXX
>>>>>FIELD01XXXXXXXXX   FIELD02XXXXX
>>>>>FIELD01XXXXXXXXXXXXXXXXXXX   FIELD02XXXXX
>>>>>

>>>>
>>>>Can you concatenate Field01 + space(n) + Field02 into Field03 prior to running the report?
>>>>
>>>>Regards,
>>>
>>>Doh! I should have added (actually I did and then deleted it) that I need to font to be different for Field02. Superscript or have the field raised slightly. That's the catch.
>>
>>In that case, you might want to look at Word automation.
>>
>>Regards,
>
>Not an option in this case I'm afraid. Simple change needed to a very complex report. Stupid Foxpro report writer...

Hi Jay,
Since you are oviosely frustrated with FRX limitations you should by all means have look at XFRX.
If you are already XFRX user, then you might find solution with their newly introduced scripting possibilities. As far as I understood you should be able to write script within report field - directly producing desired output. So I guess you can process your existing report via XFRX
adding script to that field making it appear as you want.
(I did not test this part just read about it!)

Personally I am using their PDFL library last couple of years, and whenever it comes to complex reports where I cannot achieve someting via our beloved -One&Only, I *simply* create entire report in code into PDF.
(When nicely wrapped - it is realy simple)

That is not what I am telling you to do in this case (since is just small addition) , but to consider purchasing & having yourself acustomed with. You will be less frustrated for sure when it comes to reporting :)

*** Note 4 Existing XFRX users: ****

Recently I wrapped those newly introduced xff scripts (using xFrx DEMO)
and got the same results, simplicity,precision,speed etc - as with PDFL library. What makes it *special* is that xff is an intermediate format (dbf in fact) which can be later previewed/printed/converted to all other formats.

So next to converting existing frx , you can also do full reporting cycle programmatically (bypassing frx completely) - as simple as DOS Reporting/Screen painting with old fashioned DOS commands ;

?
?? blah,blah at 
eject
@ 20,20 say blah... 
@ box(2,2 22,78 ...)

etc but this time using full page positioning in desired units.
(Pixels,units,Cm ...)

oXff=createobject... 
with oXff 
.add_page('A4')
.ln() && advance one line down (or up!)
.write_at(70,'Hello') &&Write inline - to the right 
.write_text(nFromTop,nRight , 'Hello') &&In Page Positioning 
.draw_box(nTop,nRight,nDown,nRight) &&In page Positioning
.
.add_page('A4')
.
.etc
endwith

oXff.ShowInYourOwnPreview(cResultingXff)

Those who did DOS reporting without frx will easily hint
what this can do for them ;)

This code/class will be soon posted here in downloads, so whoever wants
to experiment,betatest,feedback or contribute to this code, pls drop me an email, and I will send you full wrapper class code with reporting samples via email.