Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Solved! Yey!

Thanks to Drew's reportrunner extension, I succeeded in getting a macro to
run one specific report from a button on my forms. I edited the macro so it
would accept assigned values for DBName and aReport, then made copies of
Main () on mdlExecReport to create one for each report, which makes a
Main_Allergy () (or Main_Conditions ()...etc) selectable as a macro.

View my screenshots:

http://nabble.documentfoundation.org/file/n3679653/allergyrptbutton.png 

http://nabble.documentfoundation.org/file/n3679653/newrptrunner.png 

I needed to change the dialog a little - my application audience will mostly
be seniors - some over 90 - so it had to have the least amount of confusing
choices.

Thank you so much, Drew! Thanks, too, to Tom and Fernand and Dan for helping
out.

Beth

--
View this message in context: 
http://nabble.documentfoundation.org/Triggering-reports-from-html-files-tp3654402p3679653.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.