Hello, [EMAIL PROTECTED] wrote:
[...] > But someting is really strange here. > > The order.rml resides in /usr/local/tinyerp/4.2/server/bin/addons/sale/report > I have edited the order.rml. When logging into my test db all works fine. The > space is printed. However, when logging into my main db which I am working > with it does not. Reports in the main db have been edited with the OOReport > Designer and the send to server function has been used. > > To me it appears that reports edited with the OOReport Designer and with sent > to server are stored at a different location. I can rename the order.rml in > /usr/local/tinyerp/4.2/server/bin/addons/sale/report to backup_order.rml and > the Sale Order still prints. But it should not. When logging into the test > db, the sale order does not print. Only after renaming the backup_order.rml > to order.rml it works as it should. > > It does not surprise me that OOReport-Designer does not modify the distributed .rml files. Apart from security issues that would also be "bad" design. I'm just guessing, but perhaps the rml-data is stored in the db? > PS. After nearly 3 months, spending EUR500 and several revsions from Tiny I > still have no working version. Most of the problems with the OOReporters as > listed here are still there: > http://tinyerp.org/forum/topic5201.html?highlight=openoffice%20report%20desinger > To me, reporting in tinyerp feels like a hack klugded in without too much forethought, with numerous rounds of incremental fixes applied. For one thing, the included RML "engine" seems to have not too much in common with the thing documented at reportlab.com, their rml2pdf converter is a commercial product, so I guess someone at tinyerp re-implemented something like that. This engine works somehow, but has serious problems breaking paragraphs, dealing with templates etc.., and usage of [[/]] to escape python code has it's own problems. Things like including sums at page break are not supported or at the very least very non-obvious to implement. Adding custom fonts needs changes to source. Then there is that "other" method of creating reports (xml/xsl). After much frustration, I managed to get something together that prints on our corporate paper, has most stuff at the right place and looks nice most of the time. </rant> To be fair, with some experience and willingness to hack some "RML" and python code it should be possible to satisfy most reporting needs. Using OO to create RML-templates seems to be just another kludge... regards, Robert _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
