Report design issues - advice please?

TdeV

New member
Local time
Today, 03:17
Joined
Mar 28, 2008
Messages
4
My application has 12 main tables, 8 join tables connecting the main tables, 8 tables of attributes about the main tables, 21 note/classification tables, and 1 type table. The application provides relationships between data and does _no_ updating. In order for the data to report correctly, subreports are necessary.

I wish to create one report for a Section of data. There are 3 report possibilities:
1. Report of "section" item in one table, with all connections to items in main tables;
2. Report of "section" item in one table, with all connections to items in main tables and connections to items in attribute tables and note/classification tables, omitting printing of Description fields for all tables;
3. Report of "section" item in one table, with all connections to items in main tables and connections to items in attribute tables and note/classification tables, including printing of Description fields for all tables;

My questions are as follows:
1. Should I be building the report in Access or Crystal? (I have a licence for both, but so far have only used Access).
2. Can these options be built into one report, or do I need multiple reports? I.e. I could build the report with Subreport A) including a report on a main table and Subreport B) including a report on a main table, attribute table, note and classification tables. Are there better ways to do this?
3. How do I make the Description field, printable or not, flaggable at run-time?

Thanks for any help you can give me.
 

Users who are viewing this thread

Back
Top Bottom