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




On 2012-04-18 06:13, ptoye wrote:
Pertti Rönnberg wrote

Well said Peter!

I totally and completely agree with you and Ian Whitfield.


Well, someone likes me! My point is that I'm really a hacker when it comes
to databases, not a professional coder, and life really needs to be made
easier.

I'm almost thinking of installing something like MySQL and writing my own
front-end in Java.
That's what I did, but front end in Apache/PHP. Take it anywhere, easily migrate, update. Data security (from fall over and future proofing. Divergence not an issue.)

Steve

Is there any point in suggesting that LibO and OO should continue to
diverge? I'd have thought convergence would be more productive, both in
terms of the development which seems too thinly spread, and for users who
might even see a serious contender emerging.

-----
Peter
--
View this message in context: 
http://nabble.documentfoundation.org/Problems-importing-an-OO-database-into-LO-tp3890826p3918036.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.