Hi :)
It looks like most of this can be done without touching Base itself?  Is LO 
able to use databases in this way already?  Is it something that could be 
passed to the devs list an/or the BoD discussion list?  Something like this 
could be phrased to capture the imagination,  Saying it's the old way might put 
them off.
Regards from
Tom :) 


--- On Tue, 17/4/12, Andreas Säger <[email protected]> wrote:

From: Andreas Säger <[email protected]>
Subject: [libreoffice-users] Re: Problems importing an OO database into LO
To: [email protected]
Date: Tuesday, 17 April, 2012, 17:14

Am 17.04.2012 17:38, Tom Davies wrote:
> Hi :)
> Would it be easy to upgrade the HSqlDb embedded in Base or would all the 
> tweaks need to be applied?  Are the tweaks vital or could they left out?
> Regards from
> Tom :)
> 
> 

The easiest improvements in my honest opinion:
- Wipe out the .odb container all together and get back to the configuration of 
database access in OOo 1. Back to external databases with configuration data in 
configuration files, forms and reports in stand-alone office documents. More 
speed more safety, security, accessibility and transparency. People who do not 
understand how to connect separated software tools do not understand the .odb 
container neither (as we can read in all the mail merge topics).
- Remove all the half done wizards. Do not improve them. Remove! No database 
developer nor interface designer needs all this stinky rubbish. There are 
graphical tools to compose forms and reports within office documents. There is 
SQL for all the rest, including all the things we can not do in the current 
graphical interface. There are plenty of SQL editors to produce valid SQL for 
various databases. SQL text can be pasted into any database configuration.
- Add native database queries, so the current "direct SQL mode" returns 
editable row sets and the (useless or even harmful) graphical query designer 
can be removed as well.
- Having removed all the wizards (they are Java components) without losing any 
functionality at all, extensions could substitute .odb packages. When you open 
the extension, the database gets installed _permanently_ (rather than 
_temporarily_ like the .odb) into the configuration tree together with the 
forms and reports documents. The database will be registered and all the 
tables, queries, forms and reports are accessible form the data source window, 
hyperlinks and desktop links just like it used to be in OOo 1.


-- For unsubscribe instructions 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

-- 
For unsubscribe instructions 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

Reply via email to