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


Oops!  I meant to send this to the list.

On 04/27/2013 08:53 PM, Michael Lueck wrote:
Greetings,

At one client, this week's production check-in of an application
developed in MS Office (mostly Access) 2007/2010 code is now up to:
110,315 LOCs, 380 Modules, 249 Stored Procedures, and counting...

This is a client/server application backing up to a SQL back-end database.

I am interested in the capabilities of LibreOffice Basic along the same
lines.

The documentation for LibreOffice Basic seems very space compared to MS
VBA.

Does LibreOffice Basic even support Object Orientated Class development?
I have double class wrapped each logical type of data record. One level
is the DB table class, which manages INSERT / UPDATE / SELECT type
operations with a consistent interface. The next class layer is a
Validation class which handles DB class to Form Control mapping
(to/from) and also performs data type validation on the fields, marks
bad data fields red/error, and so on. Also I make extensive use of
in-memory collection classes: Thing / Things classes, where the Things
class contains one/many Thing class object instances.

What sorts of database drivers are available cross-platform? (Linux and
Windows) I use a mix of ADO and DAO drivers for VBA code. ADO Command /
Parameter objects when possible, ADO Recordset objects second. Both of
these ADO options leave the data in VBA variables, so works very well
for record INSERT / UPDATE forms. For Multiple Items forms displaying a
read-only list of records I use nested DAO.QueryDef objects to issue
queries in Pass-Through mode to execute a Stored Procedure, then an
outer DAO.QueryDef wrapper to copy selected records into an FE DB temp
table for local display. At first I would like to use MySQL as the BE DB
for use with LibreOffice.

TIA!

Sincerely,


This is what I was told when I asked about the capabilities of Base:

"
Le 17/02/2013 02:38, Mark LaPierre a écrit :

Hi Mark,


Now how do I create non-linked tables inside the same DB?

How do I link to another external spreadsheet using the same DB?


You would be better off using an external HSQLDB instance to link
directly to text tables (note that these would not be Excel files). See
the HSQLDB manual for how to do this.

http://hsqldb.sourceforge.net/doc/guide/guide.html#texttables-chapter


Can I link to only one spreadsheet at a time?


In a single ODB file with the embedded hsqldb engine, AFAIK yes.




 From your email I gather that all tables must be tabs on the one
spreadsheet that is linked.  Is that a true statement?  Seems pretty
inconvenient.



It is, fairly. But LO Base is not Access, nor FMPro. If you need to work
comfortably with and edit multiple separate data sources, using the
embedded hsqldb is probably not the best choice.

Alex"

YMMV

--
    _
   °v°
  /(_)\
   ^ ^  Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/
****

--
    _
   °v°
  /(_)\
   ^ ^  Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/
****



--
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.