>>Reports are for printing on paper, forms are for showing on screen. Report Preview is for eyeballing before committing to paper.
>
>sounds like an absolute. In fact, most reports that don't print more than about 80 characters on one line will look fine at 800 x 600 screen resolution.

Yeah it does soudn like an absolute. And if it causes one person to think twice about doing that then it has done the job I want it to, that is make people think before acting.

I have no problem with anything anyone does, as long as they are ready to explain why. I have a problem when folks do something and they don't know why they did that way.

>I'm having trouble visualizing a form that would present the typical tabular data that I include in a report. If you have time to describe such a form briefly that would help me.

My point is that as soon as I decide to use a form for the user to review data, the tabular issue becomes open for review. Deciding to use a form opens the possibility for an interactive question as they go type of interface as opposed to the tell me what you want and then here it is approach of reports.

I might use a grid, I might not, it all depends on the nature of the data and the best way to present it. But getting the form to look like a report would not be a majort design goal. Getting an interface that allows the user to review the data they are interested in would be the major design goal.