Can anyone provide some insight into how to create a robust reporting module? I'm imagining a solution that is able to pull from multiple tables by importing into a reporting table and then being able to sort and summarize.

Any tips and tricks?

Thanks

Just to clarify, do you want to have a separate table where each record is a separate report created by going to the rest of the database and saving the necessary information, or do you want a dynamically generated report as you would using sub-summaries and the like?

The latter.

I think Bruce's technique could be adapted.

http://fmforums.com/forum/showtopic.php?tid/198958/

It might. Bruce's solution has been sitting on my desktop, just waiting for a day of investigation. I suspect it's going to change how I handle some things so I'm reluctant to pick it up just yet.

I was really hoping for a commercial solution to drop into place, like Sindelar's SeedCode Calendar.

Perhaps a reporting module like I'm imagining is a niche waiting to be filled.