Thanks Mark, that certainly looks interesting. I may just check it out. Even so, that puts a damper on a short-term solution.
On Fri, Jul 19, 2013 at 4:51 PM, Mark LaPierre <[email protected]> wrote: > Hey Don, > > I've not bought one yet, but this is the best reference I've found out > about for LO Base. It's based on OOo Base, but that's most likely not a > real issue. The one biggest problem with LO Base is the decided lack of > documentation. > > http://www.amazon.com/s/ref=**nb_sb_noss?url=search-alias%** > 3Dstripbooks&field-keywords=**Database+Programming+with+** > OpenOffice.org+Base+%26+Basic+<http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Dstripbooks&field-keywords=Database+Programming+with+OpenOffice.org+Base+%26+Basic+> > > > On 07/19/2013 04:31 PM, Don Parris wrote: > >> Thanks Andrew, >> >> So far, none of the links really strike me as helpful. Sorry, but this is >> fairly new territory to me. >> >> I had hoped I would find a tutorial something along the lines of: >> We're going to create a way for users to enter/update data across a few >> tables in a single transaction. >> Here's how you do it using macros/BASIC... Here's how you do it using the >> DB's native capabilities... >> In order to stop our form from entering the data into each field as we >> type, we need to do so and so... >> Now to collect all the data and click submit... >> >> How does one prevent the form "inserting" the data "on the fly" - do I use >> a macro? Should I write a function or procedure on my PGSQL server to run >> when the user clicks "Submit" in the base form? And how do I get the >> "Submit" action down to Postgres to run the transaction procedure? >> >> I get the commit() function ( >> http://wiki.openoffice.org/**wiki/Documentation/DevGuide/** >> Database/Using_DBMS_Features<http://wiki.openoffice.org/wiki/Documentation/DevGuide/Database/Using_DBMS_Features> >> ). >> .. >> >> But isn't there a "BEGIN" statement? >> >> I think what I will do is move my DB forward at its current level and read >> up on transactions, triggers and procedures - as well as on LO Basic & >> Macros - so I can implement the transaction stuff later. I bet it's a lot >> simpler to understand than I think. But having to look in 20 different >> locations for little pieces of info - and then figure which pieces go >> where >> in my problem is more than I really have time for right now. >> >> If & when I do figure it out, I'll have to write a tutorial on it for >> sure. >> >> Regards, >> Don >> >> >> On Fri, Jul 19, 2013 at 8:56 AM, Andrew Douglas Pitonyak < >> [email protected]> wrote: >> >> The ODF Authors are working on a DB guide, I do not know the current >>> state >>> of it, have you looked for it (or at it)? >>> https://wiki.**documentfoundat**ion.org/images/**5/50/BH40-** >>> BaseHandbook.odt<http://documentfoundation.org/images/**5/50/BH40-BaseHandbook.odt> >>> <https://wiki.**documentfoundation.org/images/** >>> 5/50/BH40-BaseHandbook.odt<https://wiki.documentfoundation.org/images/5/50/BH40-BaseHandbook.odt> >>> > >>> >>> >>> These may also be of interest: >>> >>> http://wiki.openoffice.org/****wiki/Documentation/DevGuide/**<http://wiki.openoffice.org/**wiki/Documentation/DevGuide/**> >>> Database/Using_DBMS_Features#****Transaction_Handling<http://** >>> wiki.openoffice.org/wiki/**Documentation/DevGuide/** >>> Database/Using_DBMS_Features#**Transaction_Handling<http://wiki.openoffice.org/wiki/Documentation/DevGuide/Database/Using_DBMS_Features#Transaction_Handling> >>> > >>> http://wiki.openoffice.org/****wiki/Documentation/DevGuide/**<http://wiki.openoffice.org/**wiki/Documentation/DevGuide/**> >>> Database/Using_DBMS_Features<h**ttp://wiki.openoffice.org/** >>> wiki/Documentation/DevGuide/**Database/Using_DBMS_Features<http://wiki.openoffice.org/wiki/Documentation/DevGuide/Database/Using_DBMS_Features> >>> > >>> http://www.openoffice.org/api/****docs/common/ref/com/sun/**star/**<http://www.openoffice.org/api/**docs/common/ref/com/sun/star/**> >>> sdbc/TransactionIsolation.**html<http://www.openoffice.** >>> org/api/docs/common/ref/com/**sun/star/sdbc/**TransactionIsolation.html<http://www.openoffice.org/api/docs/common/ref/com/sun/star/sdbc/TransactionIsolation.html> >>> > >>> >>> >>> This document mentions transactions in passing >>> http://www.baseprogramming.****com/OOBasicDatabaseDev.pdf<htt** >>> p://www.baseprogramming.com/**OOBasicDatabaseDev.pdf<http://www.baseprogramming.com/OOBasicDatabaseDev.pdf> >>> > >>> >>> >>> I do not remember if I discuss transactions at all in AndrewBase.odt >>> >>> >>> On 07/18/2013 04:05 PM, Don Parris wrote: >>> >>> 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 >>>> >>>> >>> -- >>> Andrew Pitonyak >>> My Macro Document: >>> http://www.pitonyak.org/****AndrewMacro.odt<http://www.pitonyak.org/**AndrewMacro.odt> >>> <http://www.**pitonyak.org/AndrewMacro.odt<http://www.pitonyak.org/AndrewMacro.odt> >>> > >>> Info: http://www.pitonyak.org/oo.php >>> >>> >>> >>> -- >>> To unsubscribe e-mail to: >>> users+unsubscribe@global.**lib**reoffice.org<http://libreoffice.org> >>> <users%**2Bunsubscribe@global.**libreoffice.org<users%[email protected]> >>> > >>> Problems? http://www.libreoffice.org/****get-help/mailing-lists/how-to-* >>> *** <http://www.libreoffice.org/**get-help/mailing-lists/how-to-**> >>> unsubscribe/<http://www.**libreoffice.org/get-help/** >>> mailing-lists/how-to-**unsubscribe/<http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/> >>> > >>> Posting guidelines + more: >>> http://wiki.**documentfoundati**on.org/**<http://documentfoundation.org/**> >>> Netiquette >>> <http://wiki.**documentfoundation.org/**Netiquette<http://wiki.documentfoundation.org/Netiquette> >>> > >>> List archive: >>> http://listarchives.**libreoff**ice.org/global/users/<http://libreoffice.org/global/users/> >>> <http://**listarchives.libreoffice.org/**global/users/<http://listarchives.libreoffice.org/global/users/> >>> > >>> >>> All messages sent to this list will be publicly archived and cannot be >>> deleted >>> >>> >>> >> >> > > -- > _ > °v° > /(_)\ > ^ ^ Mark LaPierre > Registered Linux user No #267004 > https://linuxcounter.net/ > **** > > > -- > To unsubscribe e-mail to: > users+unsubscribe@global.**libreoffice.org<users%[email protected]> > Problems? http://www.libreoffice.org/**get-help/mailing-lists/how-to-** > unsubscribe/<http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/> > Posting guidelines + more: http://wiki.**documentfoundation.org/** > Netiquette <http://wiki.documentfoundation.org/Netiquette> > List archive: > http://listarchives.**libreoffice.org/global/users/<http://listarchives.libreoffice.org/global/users/> > All messages sent to this list will be publicly archived and cannot be > deleted > > -- 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: [email protected] 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
