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


Hi :)
If you are looking for a good guide about Macros then Andrew Pitonyak's guide is supposedly the best
https://wiki.documentfoundation.org/Documentation/Other_Documentation_and_Resources#Programmers
Apparently it is well worth the money but you might want to have a quick look at the official 
guides for free first.  Andrew wrote most of the chapters about Macros in those too as a first step 
into understanding Macros

So, start with Chapter 9 of the Getting Started Guide
https://wiki.documentfoundation.org/Documentation/Publications#Getting_Started_with_LibreOffice
Maybe have a look at Chapter 12 in the Calc Guide
https://wiki.documentfoundation.org/Documentation/Publications#LibreOffice_Calc_Guide
because spreadsheets and databases share some common ground i suspect.  Also this whole handbook 
might be helpful!!
https://wiki.documentfoundation.org/Documentation/Publications#LibreOffice_Base_Handbook

Note that the entire Base Handbook has been updated for the 4.0.x branch of LibreOffice already 
even though individual chapters were not done separately.  If you want the separate chapters you 
can always get the almost identical ones for the 3.5-3.6 branches.  

I'm not entirely sure any of this helps you but hopefully others will appear later to let you know 
if you really do need macros.  Obviously Python is a more useful language once you have gotten to 
grips with it but Basic might be easier to learn
Regards from 
Tom :)  





________________________________
From: Don Parris <parrisdc@gmail.com>
To: users@global.libreoffice.org 
Sent: Thursday, 18 July 2013, 21:05
Subject: [libreoffice-users] Base & PostgreSQL Transactions


Hi all,

I have a 4-table DB in PostgreSQL to which I connect using LibreOffice
Base.  I have a form with 2 subforms in place that allows me to:
Select an existing entity (from the ENTITY table)
Add a new financial transaction (to the TRANSREC table)
Add new line items for each transaction (to the TRANSDETAILS table).

I would like to take advantage of PostGRESQL's underlying transaction
(start, rollback, commit, etc.) to ensure that a given transaction and its
line items are entered as one single transaction.  I just don't know how to
implement that using Base as a front-end.

Maybe I really need something like macros and BASIC or Python to make such
a thing work?  If anyone knows a good tutorial on this subject, I can
certainly read - just haven't really found anything yet.


Thanks!
Don
-- 
D.C. Parris, FMP, Linux+, ESL Certificate
Minister, Security/FM Coordinator, Free Software Advocate
http://dcparris.net/
<https://www.xing.com/profile/Don_Parris><http://www.linkedin.com/in/dcparris>
GPG Key ID: F5E179BE

-- 
To unsubscribe e-mail to: users+unsubscribe@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



-- 
To unsubscribe e-mail to: users+unsubscribe@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.