I would do variable lookup listviews. Very quick and easy to do what you want to do. I use six in a weekly schedule format for each day of the week.
Dan Goldberg From: [email protected] Sent: Monday, April 04, 2011 12:56 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Design ideas please? This is the first time in a long while that I've asked for design ideas, but this one has me totally stumped on how best to present info to the user. You'll see in my last post about whether reports refresh that I'm not sure whether I want to present this info on a form or on a report (all this data is read-only). I might have to go with a form simply because the data needs to automatically refresh every 10 minutes, with no user pressing a button. A form timer can do that, don't know how a report can be refreshed. As simply as possible (I know this might be hard to describe): I have a list of parts, with a few pieces of information specific to that part. There will be 4 multiple-row "regions" of data for that part, totally unrelated information that has to be presented in different "regions" or "grids" or whatever. There won't always be data in each of those 4 regions. I must show ALL the data on the screen. So NO scrolling through a list of parts to display the other data (or else I could create a simple form with a few regions or grids). I hope this formats, but as an example using just 2 regions of information, just imagine 2 more to the right: 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 So, has anyone out there displayed that much information on a form? I am considering designing a wide temporary table and forcing the data into it row by row. I did something similar at another client. But hoping for a less "brute force" way of doing it. And I'm assuming that I won't be able to use a report (I think subreports could go side by side in detail, but haven't tried this) because of the time refresh issue. Will entertain all ideas!! Karen
