You may find that the database 含むd in OpenOffice (and Libre Office, I believe, but I make no procises for that variant) delights you as much as it has me. This page tries to help you use it.

Remember that Open Office, 含むing ooBase, is 解放する／自由な. Don't let that fool you, though. Big organizations, 政治の and 非軍事の, have 可決する・採択するd it as their 基準 office 控訴... and saving million$, but still Getting The 職業 Done. And making things 平易な for 使用者s on different 壇・綱領・公約s... Linux, Mac, Windows all spoken here!

There's more about ooBase in the main 索引 to this 構成要素. Adabas? 星／主役にする Office? 古代の history.

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 fully explained, and there are more tips, at my 力／強力にする Browsing page.)

Page contents © TK Boyd, Sheepdog ソフトウェア, 10/12-7/15.

Overview

I seem to revisit the 事柄 of "関係s" (in the database 状況!) 繰り返して.

Perhaps because they are so important?

I will direct you to more 詳細（に述べる）d essays in a moment, but first, an 試みる／企てる to explain the basic 概念 concisely.

In simple 条件...

... leaving out some of the 可能性s....

To talk about "関係s", you need at least two （米）棚上げする／（英）提議するs in your database. (条件 put in bold typeface the first time they are used are used throughout this page in the 狭くする, database, sense of the 称する，呼ぶ／期間／用語.

Imagine a database to 跡をつける what gold メダルs were won by whom during an Olympics....

For this you could use a schema with two （米）棚上げする／（英）提議するs in it. There would be one （米）棚上げする／（英）提議する with a 選び出す／独身 記録，記録的な／記録する for each competitor who has won even one gold. In that （米）棚上げする／（英）提議する, we'll call it "People", there would be fields such as 指名する, age, 高さ, 負わせる.

You would NOT try to have a field for "golds won". Not even a field for "how many". And certainly not 多重の fields... one for "first gold", "second gold", etc. That (poor) 解答 is fraught with problems. (For a start, how many would you 供給する for? And when someone 勝利，勝つs "too many", what would you do? And it gets worse the more you look at it.) (And neither would you want to do something 接近 makes 平易な: have several メダルs in one field, i.e. "Brown won gold in 100m and 500m"... which is a Bad Thing, too.)

Rather, you would have a second （米）棚上げする／（英）提議する, which we'll call "WonGold".

The （米）棚上げする／（英）提議する "WonGold" would have fields for "Event" and "勝利者". (Things like 50m men's sprint, 50m women's sprint, 100m men's sprint, etc, would each have their own 記録，記録的な／記録する. I.e. WonGold will have one 記録，記録的な／記録する for each of the golds to be awarded.

Please 許す me to 規定する that in the オリンピック we are discussing, there are two competitors 指名するd Joe Smith. Happily, one is 22 and the other is 25. Let's say that the Joe Smith 老年の 22 won the 50m sprint, and the Joe Smith 老年の 25 won the 100m sprint. If we filled in the "WonGold" （米）棚上げする／（英）提議する as follows....

Event           勝利者
 50m Sprint    Joe Smith
100m Sprint    Joe Smith

... it wouldn't be （疑いを）晴らす that it was different Joe Smiths.

I 収容する／認める that two Joe Smiths is a stretch, but, even if this example stretches credulity, the 状況／情勢 could arise, and 類似の things do arise, and with databases we "work smarter", and を取り引きする the "might happen" things.

Every （米）棚上げする／（英）提議する has a 最初の／主要な 重要な made up of one or more fields. (In our examples here, our 最初の／主要な 重要なs will be of the simple type: a 選び出す／独身 field.)

For the "WonGold" （米）棚上げする／（英）提議する, the 最初の／主要な 重要な could be the event 指名する. Leaving out the 事例／患者 of two competitors tying for first place, only one gold is awarded per event, and so the contents of the "Event" field will be different for every 記録，記録的な／記録する in the （米）棚上げする／（英）提議する, as is 要求するd of 最初の／主要な 重要な fields. (Of course, we'll need to 含む something to 指定する the sport. "100m" won't do... is that the 100m Field Sports sprint, or the Swimming event. Hence: "100mFS", "100mSwBS", "100mSwFS". (SWimming BackStroke, FreeStyle". See what tricks database people get up to?))

Going 支援する to the "People" （米）棚上げする／（英）提議する we're developing, I am going to 器具／実施する an 極端に simple 最初の／主要な 重要な system... but it will do for the needs of our example... The （米）棚上げする／（英）提議する "People", with some 指名するs filled in, might look like...

PrimaryKey   Age      指名する
   JoSm22     22      Joe Smith
   JoSm25     25      Joe Smith
   JaDo23     23      Jane Doe

It would be better, by the way, to work with year of birth, rather than age. One remains constant, the other keeps changing. If you went ahead with age, it would have to be "Age at time of Olympics". And what about someone who had a birthday on, say, the third day? Again... "petty"? No. These are the sort of 詳細（に述べる）s you need to …に出席する to, to build a successful database.)

With the （米）棚上げする／（英）提議するs "People" and "WonGold" 始める，決める up as above, we have a chance to use a 関係.

With a 関係 you can "tell" the database: Do not 受託する a value in the "勝利者" field of "WonGold" unless what is going in that field appears as a "最初の／主要な 重要な" in the "People" （米）棚上げする／（英）提議する.

This really is a Big 取引，協定. You may not すぐに see why... but the more you use 関係s, the more you will see what a 広大な／多数の／重要な thing 関係s are.

Just before we leave our little example, let me について言及する four things...

The code for a given person, e.g. JoSm22, can appear in the "People" （米）棚上げする／（英）提議する only once. That is in the nature of what a 最初の／主要な 重要な is.

But! There is nothing to stop JoSm22 (or any other person's ID) appearing 多重の times in the "WonGold" （米）棚上げする／（英）提議する. This is just 同様に, of course, as the 22 year old Joe Smith might 井戸／弁護士席 勝利，勝つ more than one メダル.

Next thing: Suppose you make a mistake? Suppose you discover that the third person in our 見本 data, Jane, isn't 23. She's 現実に 24... and you discover this after you have made several 入ること／参加（者）s in the database for メダルs she has won.

If you have 始める，決める up a 関係 between "People.PrimaryKey" and "WonGold.勝利者", and if you have 始める，決める it to 遂行する／発効させる "cascading updates", which is optional, then when change Jane's code to JaDo24, all of the 入ること／参加（者）s about Jane in the "WonGold" （米）棚上げする／（英）提議する will すぐに be 改訂するd, too. Fantastic! (Beware: If you have both （米）棚上げする／（英）提議するs open, do such an update, you need to... a) move out of the 記録，記録的な／記録する you have updated, to save it into the database, and then b) "refresh" the second （米）棚上げする／（英）提議する before you will see the 影響 of the cascade.)

Third thing: Suppose you are tidying things up, and incorrectly believe that Joe Smith, 老年の 25 hasn't won any メダルs, and you try to 除去する him from the "People" （米）棚上げする／（英）提議する... even though there's an overlooked-by-you 記録，記録的な／記録する in the "WonGold" （米）棚上げする／（英）提議する showing him (by his code, JoSm25) as the 勝利者 of some event? What happens if you try to 削除する Joe's 記録，記録的な／記録する from "People"? What happens is that the database says, "No, you can't. We need that ーするために tell what there is to know about this "JoSm25" who's 名簿（に載せる）／表（にあげる）d in the "WonGold" （米）棚上げする／（英）提議する." This is Good! Annoying... but good.

Fourth thing... and this is a "biggie". Take a 深い breath. Fetch another coffee. Sorry. But (again!) it is important....

Most of this page is about putting 関係s into your databases. There's another "thing" you are going to use in your work, which takes a bit of time to see as a 際立った "thing"... joins between fields. You use these while building queries. The 概念s are 類似の. The Open Office Base 道具s for managing them are 類似の. You have to keep yourself （疑いを）晴らす as to whether you are 取引，協定ing with a 関係 or a join at the moment.

Happily, the 所有物／資産／財産s of a 関係 and of a link are やめる different. If you have "a thing" and you are not sure what it is, carefully go into editing it. (I say "carefully", as you may want to "取り消す out" after looking at it, so that you don't 乱す its settings.)

A 関係 will 申し込む／申し出 you さまざまな update and 削除する 選択s. Joins can be "inner", "left", "権利", "cross", and "natural"- or not.

Even better news: If you are editing a 関係, the window 肩書を与える is "Relation Design" and for a join it is "join 所有物／資産／財産s". 平易な... when you know to worry, and know where to look!

Sadly, I only (re?)"discovered" (at a conscious level) this 決定的な distinction 1 December 2012... after more than 25 years of fighting with relational databases on and off. I don't say this to 粉々にする your 約束 in your guide... rather to 強調する／ストレス that databases are not 平易な, and if you are struggling, don't be downhearted. You don't have to stagger around struggling in the dark as I have had to. And even someone who is 混乱させるd on important major 概念s can get useful work done.

I am working 徹底的な my essays, expunging the consequences of my previous 欠如（する） of understanding. Until that 過程 is 完全にする, if you see the word "link", be 怪しげな. 関係s and joins are both "links". If I am using the word link, it isn't as （疑いを）晴らす as it should be, and you need to decide: "Is this a 関係 or a join", and proceed accordingly.

Speaking of "working through..."/ "直す／買収する，八百長をするing things", I would like to thank the people who take the trouble to 令状 to me to 警報 me to errors, or things which aren't （疑いを）晴らす. This page had some horrendously 混乱させるing errors which someone wrote to me about, sparing you trying to guess what I meant by things that said some 混乱させるing things! (And he even told me which page he was making suggestions about, and pointed me に向かって how I'd got myself 混乱させるd, while 令状ing!)

Sorry. Things get better from here!....

I hope you begin to think that telling your databases about 関係s between fields of （米）棚上げする／（英）提議するs is a Good Thing?

I seem have to 演説（する）／住所d the question of "関係s", setting them up, etc, several times over the years. (Partly because I was いつかs 現実に talking about joins.) I ーするつもりである to do some work on the に引き続いて, pare away some of the overlap. For now... Sorry!?... the three tutorials 利用できる to you are as follows. (The 肩書を与えるs are perhaps not always as indicative as they せねばならない be of the page's contents.)

Referential 正直さ: This discussion is in the form of a 事例／患者 熟考する／考慮する. It looks at using a database to 跡をつける 株式市場 投資するing, and 宣言するing 関係s comes up along the way. Not, at the moment, perhaps the best essay of the three... but やめる 焦点（を合わせる）d.

Multi-（米）棚上げする／（英）提議する Forms and Queries: This "勝利，勝つs" over the next in 存在 shorter... and is newer, and thus I knew more at the time I wrote it. I'd 示唆する you try it before you 取り組む the next one. In it you will create a database with two （米）棚上げする／（英）提議するs, and create queries and forms to 抽出する （警察などへの）密告，告訴（状） from the （米）棚上げする／（英）提議するs. This tutorial does not 伴う／関わる any 報告（する）／憶測... the "result" is a form that 組み立てる／集結するs your data in one 平易な to use window. It is a quick, "normal" tutorial... but doesn't cover everything the next one does.

Using 関係s: This is a monster... but it does cover a lot of ground.... much more than just "how to do 関係s"! It had 激しい editing in June 2007, and is more "円熟した" than the other two, perhaps. When you have a basic しっかり掴む of ooBase, and are ready to move on from simple things, and have an hour to spare, I would commend it to you. This tutorial also covers 生成するing a 報告（する）／憶測 based on a query. Although longer than the others, this is かもしれない better, may make いっそう少なく 需要・要求するs on you and your time. Try them all?!

And there's an essay on 関係s and joins in a short(er) page I've done talking about these important 概念s in general 条件.

Enjoy! I hope at least one of them has what you have come here for! Remember that this is just a "sub menu" of pages with discussions of 関係s. There's also the main menu to the Sheepdog Guides Open Office database tutorials, if you are looking for something else.

In a nutshell...

For the example developed at the 最高の，を越す of the page you'd do the に引き続いて. It is best to do it before putting data in the （米）棚上げする／（英）提議するs. If there is data which breaks the 支配する the 関係 would 設立する, you'll get an error message when you try to 設立する it. (In that 事例／患者, edit the data, try again.)

• の近くに the （米）棚上げする／（英）提議するs, but not the database.
• From the menu of the ooBase main 事業／計画（する） 経営者／支配人 window click "道具s"/ "関係s".
• If the "追加する （米）棚上げする／（英）提議するs" dialog isn't up, you can get it with "挿入する"/"追加する （米）棚上げする／（英）提議するs"
• Put the two （米）棚上げする／（英）提議するs ("People" and "勝利者s") on the Relation Designer form
• The "tricky" bit: see below: 設立する 関係
• Save the 関係. You don't give it a 指名する... it is "inside" the .odb とじ込み／提出する, with the （米）棚上げする／（英）提議するs, forms, etc, etc... but you do need to save it. (You'll be 誘発するd, if you try to の近くに without saving changes, though.)

Creating the 関係... the line from "People.PrimaryKey" to "WonGold.勝利者".....

公式文書，認める the "1" and the "n" at either end of the 関係 line.

They are 説 that for any given value, there will only be one 記録，記録的な／記録する with that value in the "People" （米）棚上げする／（英）提議する, but there may be any number of 記録，記録的な／記録するs with that value in the "WonGold" （米）棚上げする／（英）提議する.

Creating the line is 平易な... when you know how. You just...

• Put your mouse pointer on "People.PrimaryKey" field.
• Depress, and keep 負かす／撃墜する, the left mouse button
• Move the pointer until it is over the "WonGold.勝利者" field.
• 解放（する） the mouse button.

The line, with it's "1" and "n" should just appear. It doesn't 事柄 if you start at "WonGold.勝利者" and move to "People.PrimaryKey". There's only one end the "1" should go on, and ooBase will get it 権利.

Remember the point? Once this is 始める，決める up, you can't put a value in "WonGold.勝利者" which does not appear in the "PrimaryKey" field of the "People" （米）棚上げする／（英）提議する. (And there are other 利益s.)

編集（者）の Philosophy

I dislike 'fancy' websites more 関心d with a flashy 外見 than for good content. For a pretty picture, I can go to an art gallery. Not everyone has 急速な／放蕩な broadband.

I 現在の this 構成要素 in a 判型 目的（とする）d at to helping you USE it. There are two 面s to that: The way it is 分裂（する） up, and the way it is 地位，任命するd. 詳細（に述べる）s at my page about how the 構成要素 is 分裂（する） up and how it is 地位，任命するd.

Please remember the 構成要素 is copyright. (TK Boyd, 2006 and later) The 手続きs in the page just 特記する／引用するd are 示唆するd only for convenient personal use of the 構成要素, however, also....

Feel 解放する／自由な to use this （警察などへの）密告，告訴（状） in computer courses, etc, but a credit of the source, 引用するing the URL, would be 高く評価する／（相場などが）上がるd. If you 簡単に copy the pages to other web pages you will do your readers a disservice: Your copies won't stay 現在の. Far better to link to the 初めの pages, and then your readers will see up-to-date 見解／翻訳／版s. For those who care- thank you. I have 地位，任命するd a page with more （警察などへの）密告，告訴（状） on what copyright 権利放棄s I 延長する, and suggestions for those who wish to put this 構成要素 on CDs, etc. (There is at least one 刑務所，拘置所 using the 構成要素 for inmate education. 状況／情勢s do 存在する where good internet 関係s are not possible!)

Translations are welcomed. Tell me about yours, so I can 地位，任命する links to it. (More （警察などへの）密告，告訴（状） at the page about copyright 権利放棄s.)

広告 from page's editor: Yes.. I do enjoy 収集するing these things for you... I hope they are helpful. However.. this doesn't 支払う／賃金 my 法案s!!! If you find this stuff useful, (and you run an MS-DOS or Windows PC) please visit my freeware and shareware page, download something, and 循環させる it for me? Links on your page to this page would also be 高く評価する／（相場などが）上がる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.

Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. Mostly passes. There were two "unknown せいにするs" in Google+ button code. Sigh.

. . . . . P a g e . . . E n d s . . . . .