They might be highly specialised, highly-intelligent, and have no time available, but they are going to have to indulge in some sleeves-rolled-up action, no...?
One suggestion would be for them to learn how to use those features in Excel. The data that you are storing can be seamlessly transferred to Excel, where they can chart, pivot table, format, drag-and-fill, sub-total, and combine tables.
As a benchmark, if Filemaker could be integrated with Crystal Reports, for example, would they be happy with the size of that learning curve?
Or do you not yet use Filemaker, and are asking if it can provide all of those tools and features?
Yes, I am new to FileMaker Pro. I like the database capabilities. Crystal Reports is one of the software packages I considered but I didn't know if FileMaker and Crystal Reports were compatible.
My users have their sleeves rolled up everyday with research and their normal hospital rounds and scheduled meetings. They have been using Excel but were hoping for a single solution in FileMaker Pro. Seamless and Professional. Currently they cut and paste the data from multiple spreadsheets/workbooks. I think there should be a better solution.
Yet no matter how you slice it, they would still have to invest at least some time and effort setting up the report that they want. This is not avoidable no matter what approach you take.
If I can assume from your comment that they are either already proficient in Excel, or are prepared to become so, then Filemaker can be seamlessly integrated with Excel if you want to use its reporting capabilities. You would use FM to be the data store and you (or they) can set up their own spreadsheets which draw the data directly from FM using an OBDC link. Pivot Tables, charts, sub-summary reports etc can all then be made to refresh automatically, with all the features and flexibility of a spreadsheet still available.
I am a bit unclear how far their customising has to go. FM has sub-summary reporting, charting, table-linking, and field-formatting, but it is at the design level and not the kind of thing you want each user to be changing. But you would only need that if the reports were being frequently customised, and differently by each user.
You can produce suites of reports in the same database, so the oncologists have one set and the pharmacologists have another.