Okay, got it now. To do this, you'll need to generate the data into a temp table, just as for your single-table DB grid option (it would be the same solution). You'd have to number the rows to control display order and NULL out the duplicate values.
Much faster to do this with a report, so try that route, creating the report as an JPG, PDF, or (as someone suggested) an HTML file, then display that with the appropriate control inside the form. -- Larry ________________________________ From: "[email protected]" <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Mon, April 4, 2011 4:31:15 PM Subject: [RBASE-L] - Re: Design ideas please? Larry: You're saying the same thing as Dan, but I can't visualize it. Are you talking about one big wide listview, or a bunch of them? If the former, then that's what I'm already thinking of doing with a DBGrid, although it takes quite a bit of programming code to get the data loaded into the temp table row by row since the data comes from 5 different tables and have varying numbers of rows, or none at all. But if you, like Dan, are talking about multiple list views, how can you present that side by side given that one listview will have 1 row per part, the next listview could have 1 row per part, or 0 rows per part, or 20 rows per part... And the same for the other listviews. How can you present that side-by-side and have everything line up properly? Again I'll repeat my formatted list below. How could you possibly line that all up correctly using 1 listview for the descriptive stuff at the beginning, another listview for the "region #1" data, another listview for the "region #2" data? Each region has varying number of rows, and must be easy to relate back to the part# at the beginning. REGION #1 REGION #2 Part1 Part description1 12/01/2010 1500 Cary Grant phone#1 11/02/2010 500 Joe Smith phone#2 Mary Brown phone#3 Part2 Part description 2 03/15/2011 200 Rick White phone#4 04/10/2011 150 Karen I think a form will work better than a report, because of the timer issue (although, if a report can be closed from code OUTSIDE the report, you would have a form AND a report, and use a form timer to close and reopen the report). > >If you can fit all the data on one "page" of a report, I don't see why it >can't >fit on one screen. Just make the font size smaller, until it fits. It's a >matter of figuring out how many rows is the allowed maximum for each set of >data. > > >I would use Variable Listviews for the display rather than getting involved >with >adding multiple tables to the form. I think it gives more control. Just keep >setting the font size down until you have enough "rows" in the listview for >the >number of rows that will be returned. > >
