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


On Thu, 2011-10-06 at 10:26 +0100, Tom Davies wrote:

Hi :)
Is this a 1st attempt at moving away from Windows and MS Office at the
same time?  

If the database was an Access database then the Queries, Forms and
Reports don't translate easily and need to be re-created.  The data in
the Tables should be Ok and any relationships between the tables is
likely to be ok (i would check that).  



You might be able to translate the Queries by going back into Access
and view them as Sql statements and then copy&paste those into notepad
and from there into Base.  Access's Sql is quirky so it might be
better to just re-create the Queries from scratch.  

The problem with SQL is that all versions generally implement most of
the current standard but always the same parts - bad enough and more
irritating extend SQL with their own extensions which are often not
support by anyone else. All the database developers do this, even the
FOSS developers.


Moving away from Windows does kinda force you into leaving MS Office
but it's often a good idea to stay in Windows a bit longer and just
get
used to the programs first before migrating.  LibreOffice is a crucial
part of that, along with Firefox/Opera/Chrome instead of IE and
Thunderbird/Evolution/Claws for emailing.  

A lot of programs written
for Windows do work in Gnu&Linux using Wine (Wine Is Not an
Emulator (it uses a more sophisticated approach)) but MS Office,
Outlook (and Outlook Express) and Internet Explorer are 3 that don't
work well.  


Rgards from
Tom :)


--- On Wed, 5/10/11, planas <jslozier@gmail.com> wrote:

From: planas <jslozier@gmail.com>
Subject: Re: [libreoffice-users] data base program
To: users@global.libreoffice.org
Date: Wednesday, 5 October, 2011, 15:11

Chaim,

On Wed, 2011-10-05 at 13:57 +0200, Chaim Seymour wrote: 

Hi all

I set up Fedora 15 on my second computer and the Libre Office is included.

As a fountain pen collector, I started building a database for my
collection. I defined the fields and built a table. I started filling the
table, but wanted to add an extra field. To my surprise, the structure of
the db had disappeared. The table works. I can add items and alphabetize.

Can one go back and rebuild the db structure from the table and if so how
does one do it?


Right click on the table and select edit and you will see the table
design. Make your changes, adding new columns should not cause any
problems with data integrity and save. When open the database for data
entry you will see the new column. 

Thanks

Chaim

-- 
Chaim Seymour
David Elazar 8
Givat Shemuel 54032
Israel
tel: 972-3-5320560




-- 
Jay Lozier
jslozier@gmail.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




-- 
Jay Lozier
jslozier@gmail.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.