Thanks for the ideas Bernard,
Bernard Peek wrote:
-Check for verions of OOo under Linux that require some reports to be
saved to disk, before then can be printed.
( the biggest problem being "how to know all versions of OOo/OS that
have this problem" - so am thinking of just making this the process for
all printed reports
That could be a security risk. Reports are likely to contain sensitive
data.
Meaning?
- The risk being that the report is saved to disk, but due to an error
the extension fails delete it?
or
- The risk exists even if the full process runs and it is removed
(unliked on disk)?
Reports are likely to include printing invoices and cheques. Those print
runs need to be logged in a secure way. Whether building that sort of
logging into the printing system is a different question.
I was thinking of implementing this by using a database of course. Where
that database is, or what it is ( Base, MySQL, etc ) should be
configurable and this configuration should be separate from the users
OOo configuration.
In a networked environment, which is what I would expect when security
is a high requirement, the extension should be installed as a shared
resource, with the physical db and user account used for logging
configuration data available only to OOo network administrator. I
believe the new options API for extensions will allow this kind of
control - need to follow up on that with some research.
Bottom line is this needs some real thought - given the discussion
earlier regarding accounting systems and SOx compliance issues though I
think it something that needs to be addressed, in someway.
- |extended| capture user parameters used to produce report
Designate specific printer for specific reports.
Definitely. Also specify what paper stock is to be used or which tray.
Good points - I fiddled a bit with printer settings using basic a while
back and had some issues time to look at that again.
Attach to email - run the report(s) as requested, open email client
editor, attach report(s)
Mail-merge to email. Send entire report to one email address as an
attachment.
Hadn't thought about that.
Two ideas jump to mind:
Creating a Master Document. (some possibly interesting side effects or
possibilities to this approach)
Create a zip file with the different reports.
Drew
--
OpenOffice.org User Community Forums
Connecting users around the globe!
Community forum http://user.services.openoffice.org/en
Communauté francophone http://user.services.openoffice.org/fr
Közösségi fórum http://user.services.openoffice.org/hu
コミュニティーフォーラム http://user.services.openoffice.org/ja
United States PostgreSQL Association: http://www.postgresql.us/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
