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

On 07/31/2016 07:36 PM, Ken Springer wrote:
I understand the concept of Front End/Back End, but never have dealt with it. Nor have I ever used MySQL, Mariadb, or others. Access and a bit of dBase is all I've ever used, and in general, even then that's more power than I've ever needed.

Actually, IIRC, Access has both a client and server built in. The user isn't normally aware of it. In my experience with Access 1.1, the server is called the "Jet" server. Today's Access may no longer use the Jet server, but I am sure something like it is still in there somewhere. I must admit the Access bundled concept is addictive. As a newbie to databases back in the 90s, I liked it and it was a shock and a learning experience to wean myself off of it and go with the industry standard forms of client/server architecture and the SQL language. Since then I have learned a lot and find the latter concept very powerful. In your case, if Access and dBase had/have more power than you ever needed and that power is all that you will ever need, then the LO internal HSQLDB engine is probably a good choice for your application.

Now that you mentioned dBase, you may, or may not, be aware that LO has a dBase option. But a limitation to it that I found is that older versions of dBase files are not supported. I have some old dBase 1.x files with dbase programs that will not load into LO, let alone run.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.