Brent,
Jay has laid out a very detailed approach. Here's another. I'm a strong advocate of using 'report cursors' which contain all the information needed for a report. This way I don't have to set relations, use SKIP, etc. Most of my reports use a single cursor called 'rptdata'. If you carry this idea one step further, you can develop 5 cursors (one for each of your 5 reports) containing all the necessary fields. Then when writing the SELECT statement for each of the 85 projects store the information in the corrrect cursor field:

SELECT name as Contact, company as Address1........ ;
   from table Project1 ;
   Where..... ;
   Into cursor RptData

SELECT Conname as Contact, Compname as Address1..... ;
   from table Project2  ;
   Where.... ;
   Into cursor RptData

Your RptData cursor will always have the same structure for the reports, but you can map any field you want from the original tables.

HTH
Barbara

>I don't even know if this is possible.....
>
>I have 85 different projects that I need to do reporting on. The whole reason I am working on these reports is to take the 85 projects and use one to five report forms to print them, instead of 85. I need a way to print a report based on which project a user chooses. The layout doesn't really matter as long as the reports have all the data. But the fields for each project are different. They all do have some fields in common (name, agent # address), but not all. How can I make one report generic enough to be able to handle all of these projects.
>
>Any help would be most appreciated, because I am very stumped.
>
>Thanks