That looks really cool, but I think it might be overkill for what I need to do right now. I've saved the link though!

>>Thought of that, but the columns would need to be adjusted for length. I've always disliked having controls on a report or screen all on top of one another. I wonder though... Could there be different groupings for each scenario? Remove the line if blank or something like that?
>>
>>>You can have all 5 fields in the report and control with PRINT WHEN which ones to print.
>>>
>>>>We have this code in a class-level Print button. The report is setup for two columns as that is what the alias normally has. I would like to make the report form dynamic where it can handle 1 to 5 columns, depending on what's in the alias. Development time is a concern, and one developer has suggested just using different reports for each scenario. That goes against my sense of oneness with the world, so is there a non time consuming way to have one report form handle this? The data is all very similar, lookups, codes, descriptions, that sort of thing. Using VFP9.
>>><snip>
>
>Hi Jay
>
>Have look at www.report-sculptor.com
>
>Technique I suggest is exlpained here ;
>http://weblogs.foxite.com/reportsculptor/archive/2008/10/22/7142.aspx
>
>Since you are using ordinary form containers as report bands, and you drive report execution in your own code
>you can do whatever you wish.
>In this case I would design visually 'static' part of report (form containers, labels & textboxes) and then use bit of freehand
>report writing (in code) to populate columns dynamically based on content/criteria.
>
>It can be exposed via standard VFP9 preview / print or sent to PDF etc.
>All free.
>
>HTH
>Sergio