I'd probably approach it by building a cursor with the fields named COL01, COL02, COL03, HEADING01, HEADING02, HEADING03, etc. On the report, you could reference the generically named fields. Also have a variable or something that is the max count and put print whens on all the columns to suppress if the max count is less than that particular column. It's a PITA to do all that .. but I have done something similar in the past.
OR ... here's another approach ... The expression for a field on a report is AN EXPRESSION. That means it doesn't have to say MyTable.QPAC. What you can do is prepare some information ahead of time that helps figure out what goes in what column (UDF, method call, etc.). The expression for a field on the report could be EVALUATE(MyUDF(1)) for the first column, EVALUTE(MyUDF(2)) for the second column, etc. That UDF would know what field from your table needs to print and it would return the value of that field. Same with the headings .. let MyUDFHeader(##) figure out the headings. In SP2 you can take another approach which is to use one of the advanced properties features to suppress an entire column .. however .. that doesn't mean you can define the report wider than the paper and just hope you suppress enough columns to make it fit. Cathy > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of MB Software Solutions, LLC > Sent: Tuesday, September 08, 2009 5:26 PM > To: [email protected] > Subject: VFP9SP1 report -- need suggestions on alternative approach > > Check out this graphic: > http://mbsoftwaresolutions.com/images/gbr2.png > > The part circled in red shows all possible categories for that grid. > What I want to do (because we may want to add more and we're out of > horizontal report real estate) is conditionally show columns, and have > them basically be something like you'd output to Excel if you were doing > this, but only having columns where counts exist. > > Clear as mud? ;-) > > tia for ideas! > > -- > Mike Babcock, MCP > MB Software Solutions, LLC > President, Chief Software Architect > http://mbsoftwaresolutions.com > http://fabmate.com > http://twitter.com/mbabcock16 > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/003d01ca3148$12605570$372100...@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
