Page has been 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. Mostly passes.|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
You may find that the database 存在 shipped with OpenOffice (ver.2 and higher) delights you as much as it has me. This page tries to help you use it.
Forget anything you may have heard about Adabas, which （機の）カム with 星／主役にする Office, the 商業の 見解／翻訳／版 of Open Office 1. The 現在の Open Office's database, "Base", aka "ooBase", is 関係のない. And remember that Open Office, 含むing ooBase, is 解放する／自由な! But don't let that fool you. And it's not new. Big organizations, 政府 and 非軍事の, are 可決する・採択するing it as their 基準 office 控訴... and saving million$, but still Getting The 職業 Done.
There's more about ooBase in the main 索引 to this 構成要素.
This page is "browser friendly". Make your browser window as wide as you want it. The text will flow nicely for you. It is easier to read in a 狭くする window. With most browsers, 圧力（をかける）ing 加える, minus or 無 while the 支配（する）／統制する 重要な (ctrl) is held 負かす／撃墜する will change the texts size. (大きくする, 減ずる, 回復する to default, それぞれ.) (This is more fully explained, and there's another tip, at my 力／強力にする Browsing page.)
Page contents © TK Boyd, Sheepdog ソフトウェア ®, 2/06-5/200.
For many years, this was an introductory lesson at the start of tutorials by me relating to Open Office's "Base", which I usually 言及する to as "ooBase". Spring 2020: I am "making the switch", migrating to LibreOffice's Base. This essay has been editied to 反映する that.
Unfortunately, the 称する，呼ぶ／期間／用語 is used for two やめる different things.
A "database" can be some data, e.g. the 指名するs and 演説（する）／住所s of some friends or 顧客s. When I speak of a "database", I will 普通は be using the 称する，呼ぶ／期間／用語 this way.
"A database" is also a 称する，呼ぶ／期間／用語 used, some would say improperly, for the programs (i.e. 使用／適用s) which manage the data in the collection of data. I will 一般に 言及する to the programs as "the program to manage your data", or as the RDMS. ("Relational Database 管理／経営 System"). Examples of RDMSs are LibreOffice's "Base", ooBase, MySql, 接近, Paradox and Oracle. The last is for big 会社／団体s. The 接近 is expensive, and supports Mr. Gates' hegemony. Paradox's day has pased, I 恐れる, but was once an excellent choice. You could once get Paradox on eBay as part of the Corel Wordperfect 控訴, but I wouldn't recommend that today. There was a run-time 一括 which you could give away so that people could use （米）棚上げする／（英）提議するs/ forms/ etc which you developed for them, sparing them having to buy and 任命する／導入する the 十分な 一括.
The good people at Open Office 会社にする／組み込むd the HSQL RDMS in 見解／翻訳／版 2 of the 解放する／自由な, multi-壇・綱領・公約, Open Office office 控訴, and that was carried with the 製品 when LibreOffice 分裂（する） away to create it's own fork. In 2019, LibreOffice switched to Firebird. HSQL was 類似の to MySQL, and remains an 選択 for LibreOffice 使用者s. I would guess that Firebird is too, but can't tell you for sure. I would 示唆する "going with the flow", and using Firebird if you are new to LibreOffice.
An RDMS cannot 対処する with any data you may wish to manage... but it will do many important 職業s.
Most of us use a wordprocessor almost without 成果／努力. Spreadsheets are 比較して simple to use in a basic way. (And can be used for simple data 管理／経営 仕事s! Both wordprocessors and spreadsheets, of course, are also 有能な of 前進するd things. But those 使用／適用s have more gentle learning curves than databases do.)
Getting started with databases is harder... but 価値（がある） the 成果／努力!
(Apart from the acronym "RDMS", words in IN CAPS in what follows are 存在 used in a 狭くする way, as a database engineer would use them.)
The data an RDMS is good for is data which can be put in one or more TABLES. They are put together as follows. For the moment it may sound as if all you would need is a spreadsheet. 耐える with me.
A TABLE is a grid of 列／漕ぐ／騒動s arranged in columns. The 列／漕ぐ／騒動s of a TABLE will 含む／封じ込める data about one person, event, item of 倉庫／問屋 在庫／株, 調書をとる／予約する, etc, etc. Each column will give （警察などへの）密告，告訴（状） about a 選び出す／独身 （独立の）存在.
A telephone 調書をとる／予約する is a simple example of the sort of data that a RDMS can manage 井戸／弁護士席. (Although RDMSs really come into their own with more コンビナート／複合体 data.)
The elements of each 列／漕ぐ／騒動 of the TABLE, taken together, 構成する one RECORD. The columns are called FIELDS.
My RECORD in a phone 調書をとる／予約する might be:
TK Boyd....1 Main St....919-555-1212
A simple phone 調書をとる／予約する （米）棚上げする／（英）提議する like that would be said to have three FIELDS: 指名する, 演説（する）／住所, Number. (The "指名する" field might 井戸／弁護士席 be 分裂（する） into NameFirst and NameLast fields, but the 原則 is the same.)
Once you have data in （米）棚上げする／（英）提議するs, you can do さまざまな useful things with it....
Instead of working with the data in its "raw" form, instead of working 直接／まっすぐに with （米）棚上げする／（英）提議するs, you will 始める，決める up FORMS. They may 陳列する，発揮する the data looking almost as it does when you 接近 a （米）棚上げする／（英）提議する 直接／まっすぐに, but they also 許す you to 陳列する，発揮する the data in other layouts. Layouts which may better 控訴 the 使用者 in some circumstances.
You can 現在の the data to the 使用者 in different 判型s and with different SORTING or FILTERING 計画／陰謀s. (Filtering 審査するs out some of the data. For instance, a phone company knows all of its ex-directory 顧客s, but it would be a sensation if the phone 調書をとる／予約する was accidentally published without filtering those 記録，記録的な／記録するs out! In some countries, if you know a phone number, you can 協議する a "逆転する look up". Before computers made the 製品 redundant, you could buy a copy of a phone 調書をとる／予約する with the numbers 名簿（に載せる）／表（にあげる）d sorted by number rather than by 顧客 指名する. The first （米）棚上げする／（英）提議する 述べるd in these tutorials will let us 調査する sorting and filtering その上の.)
You can EDIT the data, i.e. 追加する new 記録，記録的な／記録するs, 削除する obsolete ones, change the data in some of the fields of a given 記録，記録的な／記録する, e.g. 改訂する my telephone number and 演説（する）／住所 if I move.
You can run QUERIES: Suppose you want a 名簿（に載せる）／表（にあげる） of all the people in the phone 調書をとる／予約する who live on Main St... you could use a query. (There are other ways to find the Main Street 居住（者）s, too.) (Filtering 制限するs what is 陳列する，発揮するd. A query fetches a collection of 記録，記録的な／記録するs into a copy of a 部分 of the database. A query creates a new, usually 一時的な, （米）棚上げする／（英）提議する. It isn't always a mere subset. いつかs each 記録，記録的な／記録する in the query consists of fields from more than one （米）棚上げする／（英）提議する.)
You can design and run REPORTS: A 報告（する）／憶測 design says "Print out bits from the database in the に引き続いて way....". Sheets of 演説（する）／住所 labels are produced with a 報告（する）／憶測. Mailshots with "Dear "Mr. Smith, You and two other people in Middletown have won..." are produced with 報告（する）／憶測s. Often, you will want to 生成する the same 報告（する）／憶測 from time to time. To answer this need, RDMSs give you a way to save your 報告（する）／憶測 specification so that you don't have to 繰り返して explain what you want. A 報告（する）／憶測 can also do arithmetic with suitable data. (Suppose your database covers your 株式市場 大臣の地位. If one field were "Number of 株", and another were "Price per 株", you wouldn't need a "Value of 持つ／拘留するing" field in the （米）棚上げする／（英）提議する.... any 報告（する）／憶測 could give you the holdings' values by multiplying the contents of the "Number of.." and "Price per..." fields. The 報告（する）／憶測 could also calculate the total value of all your holdings.) From the telephone numbers database, you could print a 報告（する）／憶測 of how many 顧客s lived on Main St, on River 運動, on Mountain Way, etc. 報告（する）／憶測s can be created on the results of a QUERY, for times when you only want to 含む 記録，記録的な／記録するs 会合 確かな 基準.
You are welcome to use the 構成要素 here 解放する／自由な of 告発（する），告訴（する）／料金. But if you want to show your 評価, you easily can make a gift to me or 与える／捧げる to a charity I would like to help... I've 名簿（に載せる）／表（にあげる）d several to choose from. (The link will open in a new tab or window.)
With that basic database vocabulary, you are ready to return main menu, or just jump straight into the first tutorial about LibreOffice Base and ooBase. (I've also written some 公式文書，認めるs on 任命する／導入するing OpenOffice. Something 類似の is planned for LibreOffice, but the 過程 is pretty much the same. Do be careful to 任命する／導入する the 権利 Java RTE. If you have the 64 bit LibreOffice, you need the 64 bit Java RTE. If you have a recently 任命する／導入するd 体制／機構, which seems to work, but いつかs behaves oddly, see that.)
I dislike 'fancy' websites with more 関心 for a flashy 外見 than for good content. For a pretty picture, I can go to an art gallery. Of course, an attractive 場所／位置 WITH content deserves 賞賛する... as long as that pretty 直面する doesn't cost download time. In any 事例／患者....
I am trying to 現在の this 構成要素 in a 判型 which makes it 平易な for you to USE it. There are two 面s to that: The way it is 分裂（する） up, and the way it is 地位，任命するd. See the main 索引 to this 構成要素 for more （警察などへの）密告，告訴（状） about the way it is 分裂（する） up, and the way it is 地位，任命するd.
PLEASE >>> Click here to visit editor's Sheepdog ソフトウェア (tm) freeware, shareware pages <<< PLEASE
If you liked this ooBase tutorial, see the main 索引 for （警察などへの）密告，告訴（状） other help from the same author.
Editor's email 演説（する）／住所. Suggestions welcomed! - - - Want a 場所／位置 hosted, or email? I like 1&1's services.
Page has been 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. Mostly passes.
AND passes...
. . . . . P a g e . . . E n d s . . . . .