Hi, Coming at this late...
Geert Janssens <geert.gnuc...@kobaltwit.be> writes: > For starters the user preference is an all or nothing thing, either all > reports are in a book or in a common location. That's not very fine-grained. > Perhaps you consider some reports common and some reports book-specific. This > could be solved by making it a per report option of course. I can picture very few cases where a configured report is not tied to the book. If it contains references to *ANY* accounts, then it is, by definition, book-specific and should live with the data. This is, IMHO, most reports. > And yet another issue: reports are only suitable for multiple books if these > books have the exact same base as required per report. An example to clarify EXACTLY! The only time all saved-reports are useful across books is if the books are derived from the same base. I.e., you copy, or save-as. If the reports are stored in the book data itself then you get this for free. [snip] > So my conclusion is that report configurations are essentially book specific > and should be treated as such to avoid unexpected accounting mistakes. Agreed. > On the other hand I understand it takes time to carefully configure > reports to your preference and there's a wish to reuse this effort > across books. Perhaps we need an "export report configuration" that can extract the non-book-specific settings? -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel