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.

Put your update code in the form timer as you did before.

If, for some reason, you really, really want to use the report writer, there's 
another solution.  Again, use a form and instead of listviews use one or more 
Image or PDF fields.  Then, whenever the timer fires, print your report to one 
or more image or PDF files and have the form update its images or PDF view 
fields.  An advantage here is that you can use STRETCH to guarantee that 
everything in the image field is on the screen (not withstanding that it may 
not 
be very readable if it gets too small).

--
Larry

Reply via email to