I saw this was not possible, however is there any impetus for doing this in a near future release, that is to allow multiple tables sourcing one Report.

The only thing I can think of now is to make a VIEW from all the client related tables and then map that in a report builder template.

Would be nice to create multiple reports and then combine them together, but not having our customers doing that manually.  The multiple table report makes sense because we have different client areas in separate tables such as Contact, Power of Attorney, Income, Resource, Eligibility, etc.  The customer needs to see these all on one Face Sheet.

No problem, was just asking and leaning some weight on it as a wish list item.

I'll try the VIEW, the SQL for us to do some Views can get a bit complicated and harder to troubleshoot, but it is an open option sitting there.

I had started putting multiple WPDATA tables on top of each other on the WP page so it looks like one form/template; feeding from each table multiple times to get what one template can feed/show.  The problem again is how hard it is to format it as needed.

Thanks again for your help.  BTW, you guys have the best ticketing system available, easy to use, organized and no email.

Ha, actually no.  I was trying to repeat back ideas I had to work around this.  Report Builder it turns out will not be able to make the FaceSheet.  The problem or complexity is that a VIEW will not work due to the different table designs.  We have a VIEW that does some subtotaling, and I am not sure if it is impossible or way too complex to add the other tables.

The other way was to add WPDATA tables on the page one after the other to create the rows and that leads to another open ticket about Column Width which you saw by now so you can close this one out.  Thanks!

I think we can close this one out, I may keep banging my head on it.  I end up getting searches taking me into StackOverflow and the geniuses there can get one depressed and confused, some do help.

The Views have been created to show Incomes with subtotals and another View for Resources with subtotals by customer, but I have to marry them into one View and then add the Customer fields like Facility, Name, Phone, Email, and more.  Having the tables from where all that data comes from in one Report Builder I think would be great to solve that dilemma.  Your SQL is appreciated, I need to make sure I can understand it fully and handle it, so I can edit it and add to it, etc.  Things can get complex real fast and troubleshooting gets tougher, plus something else may fire and then I end up launching searches.

Thanks again.

Thanks Aleksandar for the explanation, it does confirm what I was also thinking.  I took a crash course in Foreign Keys even though I worked in lots of databases from Oracle to SQL server.  I never used Joins as the easy way, I learned to use the Keys though and their relationships.  Like ID1 = ID2 in MS access and that sets the relationships and using flat file via Unix, we used ID1 = ID but you had to know the many to 1 or 1 to 1 in the WHERE.  All that time I could have used INNER JOIN.

I think pulling these tables together will be too messy, I tried things like this before and it takes a lot of attempts which I will see if I have the time.  Hah, and patience!  It is the idea that the two tables have multiple rows with a customer ID where the other tables have 1 record per customer and the VIEW is the only thing in WPDATA that can be used when doing the subtotaling, yet Views have to have the same number of columns.  Oh well.

You can close this one out, thank you.