This is Sky. "skywoof.com" is 指名するd for her. (^_^)|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
You may find that the database 含むd in OpenOffice 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 ソフトウェア, 2012- 損なう 2025.
This page is not of my usual style. There is little "now type this" 構成要素 here. You will find several other pages どこかよそで on the 場所／位置 with that type of 贈呈 in 関係 with 関係s and joins.
As soon as you go beyond the earliest "はうing" 行う／開催する／段階 in using Open Office Base, or any other relational database... there's a hint in the 指名する... you will begin using more than one （米）棚上げする／（英）提議する in your database. (Beginners いつかs think that a （米）棚上げする／（英）提議する is "a database". While some very, very simple databases only have one （米）棚上げする／（英）提議する, they are very 限られた／立憲的な. Even if they can be useful.
As soon as you "前進する" (begin to totter like a toddler) to having 多重の （米）棚上げする／（英）提議するs in your database, 関係s become enormously important. You aren't 現実に 要求するd to have them, but it would be foolish to have a multi-（米）棚上げする／（英）提議する database without setting up 関係s. And the more you use them, the more you will see how useful they can be. Many things which you will want to do will 要求する the presence of 関係s. You might 同様に start using them, even if, at first, in a 限られた／立憲的な way, as soon as you start making multi-（米）棚上げする／（英）提議する databases.
(We'll get to "joins" later.)
The computer can't read your mind.
Let's say you have a database for 調印 調書をとる／予約するs out of a public lending library. A very simple database!
It could rely on each 調書をとる／予約する having a unique ID printed in the 調書をとる／予約する. It, the 調書をとる／予約する's 肩書を与える, etc, etc, would of course also be in the computer... but for our 目的s it doesn't need to be. 公式文書，認める, though, that the ISBN alone won't do. Each 調書をとる／予約する in the library must have a unique ID. That could （米ソ間の）戦略兵器削減交渉 with the publisher-割り当てるd ISBN... but then the library would have to 追加する something like -1, -2,-3... to distinguish 多重の copies of that 調書をとる／予約する, if the library had them.
So... still no （米）棚上げする／（英）提議するs!
There would a （米）棚上げする／（英）提議する with the 詳細（に述べる）s of the people with 許可 to borrow from the library... their 指名するs, 演説（する）／住所s, phone numbers, etc. AND a unique- to- each- person "ID code". We'll call the （米）棚上げする／（英）提議する "顧客s", and the 顧客 ID "CustID".
The only other （米）棚上げする／（英）提議する we need is a "BooksOutOnLoan" （米）棚上げする／（英）提議する. In a SIMPLE lending database, we would need only two fields: 調書をとる／予約する and Borrower.
BooksOutOnLoan.調書をとる／予約する would be the （米）棚上げする／（英）提議する's 最初の／主要な 重要な... a given 調書をとる／予約する can only (in our 代案／選択肢 universe) be on 貸付金 to one person at a time, and we aren't going to try to 跡をつける lending history. The other field will have a person's ID code entered in it.
If four 調書をとる／予約するs were on 貸付金, the BooksOutOnLoan （米）棚上げする／（英）提議する might... if you had designed your ID coding very 不正に.. look like...
調書をとる／予約する Borrower
BK003 Pers528
BK106 Pers528
BK007 Pers312
BK823 Pers492
I hope you see that the above "says" that one person (Pers528) borrowed two 調書をとる／予約するs, and two other people each borrowed one 調書をとる／予約する. If you don't see that, struggle with it until you do, because it is important to things to come.
Now... you could run the database just like that.
But it would be so much better if you define a 関係 which says that any 入ること／参加（者） in BooksOutOnLoan.Borrower has to be a string of characters which occurs somewhere in the 顧客s.CustID field.
公式文書，認める I said "if you define a 関係". It is up to you. The computer can't read your mind. You have to tell it that the field "Borrower" in the （米）棚上げする／（英）提議する "BooksOnLoan" will should only ever 持つ／拘留する values 設立する in the "顧客s" （米）棚上げする／（英）提議する, in the "CustID" field. 論理（学）の enough. A human would "just know".
The 広大な／多数の／重要な thing is: Once you have put the 関係 into the database, it won't LET you put bad data into the BooksOnLoan （米）棚上げする／（英）提議する!
A given database may have many 関係s. The above was just a simple example.
The 詳細（に述べる）s are covered in さまざまな tutorials, but just to get the impatient started: You 接近 the 道具 for telling the computer about 関係s you want it to know about by going to the ooBase main 事業／計画（する） 経営者／支配人 window. From its menu, you click "道具s"/ "関係s".
Moving on... but still talking about 関係s.
When you have a 関係s 始める，決める up in a database, you can 始める，決める it to 遂行する／発効させる cascading updates, and/ or cascading deletions.
Suppose in your database, you had a （民事の）告訴, and some 顧客 didn't like the 顧客 ID you'd given then. Maybe you gave them "Pers911", and they have 特に unhappy memories of that day, and want a different 顧客 ID. But they already have some 調書をとる／予約するs out on 貸付金. (This is a わずかに stretched example! But I hope you will be able to see how cascading could be useful in other circumstances!!)
Suppose "Pers876" hasn't been 問題／発行するd yet, and the 顧客 would be happy with that. You change the 入ること／参加（者） in the "顧客s" （米）棚上げする／（英）提議する. Do you then need to go into the "BooksOnLoan" （米）棚上げする／（英）提議する, and change any instances of Cust911 to Cust876? No, you don't... not if you have 始める，決める the 関係 up to 遂行する／発効させる cascading updates. Pretty 冷静な／正味の, really. And it helps you keep the data in your database "good".
Joins are a little like 関係s. Too much like 関係s, for me, because I often get 混乱させるd. Which I shouldn't. They really are 明確に different. But I do.
Joins become important when you are building a query or a 報告（する）／憶測 which draws on 構成要素 from more than one （米）棚上げする／（英）提議する. For the library, you might want to be able to produce....
調書をとる／予約する Borrowed by
BK003 Doe, John
BK106 Doe, John
BK007 Smith, Francesca
BK823 Brown, Rebecca
Very nearly what we had before... but we have 代用品，人d the 顧客's 指名するs for their IDs. (We have the 指名するs in the "顧客s" （米）棚上げする／（英）提議する, too.)
"All" it takes is a join between BooksOutOnLoan.Borrower and 顧客s.CustID. That join will be very 類似の to the 関係 we 始める，決める up between them earlier. If you create the 報告（する）／憶測 by making a query first, and then doing the 報告（する）／憶測 on the query results, then whether you create the query in design 方式 or with the wizard, Base will "slip the join in" without telling you what it is doing. The join will show in the query design 審査する, but unless you look closely, it looks like a 関係. But it is not the same thing!
I am out of both time and energy. I am going to stop there. You've had the important "長，率いるs up": Start getting these TWO things, 関係s and joins, separate in your mind. There is much about 関係s, and a growing 団体／死体 of stuff about joins in my さまざまな tutorials.
A 嘆願: If you come across the word "link", where I might have meant "関係", or I might have meant "join", please send me the page's URL ("www-thingie")? That will have been from the Bad Old Days before I knew there were two （独立の）存在s, and began to distinguish between them. The ambiguity and 混乱 need （疑いを）晴らすing up!
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!)
If you liked this ooBase tutorial, see the main 索引 for （警察などへの）密告，告訴（状） other help from the same author.
Search SheepdogGuides.com 場所／位置, 含むing Flat-Earth-学院...
|
What's New at the 場所／位置 / / 前進するd search
This search 道具 (解放する／自由な to me and to you) is 供給するd by FreeFind.com... whom I've used since 2000. I'm happy with them... 明白に!
Unlike the clever Google search engine, FreeFind's 単に looks for the words you type, so....
* （一定の）期間 them 適切に.
* Don't bother with "How do I get rich?" That will 単に return pages with "how", "do", "I"....
公表，暴露: FreeFind tells me what people have searched for. It doesn't tell me your personal 詳細（に述べる）s. (If someone would "秘かに調査する" on you, wouldn't they also feel 解放する／自由な to 嘘（をつく） in a "privacy 声明"? Not to say I'm not lying... how can you tell?... but to say "What are privacy 声明s 価値（がある）?".
Please also 公式文書，認める that I also have other 場所／位置s, and that the FreeFind search will not 含む results from them. They each have their own 場所／位置-明確な／細部 search buttons.
My "wywtk.com" 場所／位置...WhatYouWantToKnow
My "skywoof.com" 場所／位置...
This is Sky. "skywoof.com" is 指名するd for her. (^_^)
And there are links from those pages to pages at my SheepdogGuides.com, Arduserver.com and Flat-Earth-学院.com 場所／位置s, which are also controlled by me.
https://www.arunet.co.uk/tkboyd/ My oldest-still-running 場所／位置*. Have a laugh at some 時代遅れの 構成要素! It may be 時代遅れの in styling, but not all of the content is obsolete. Much of what was there is also 利用できる at https://skywoof.com/aru/index2.htm (*My Compuserve 場所／位置 is, 式のs, history.)
To email this page's editor, Tom Boyd.... Editor's email 演説（する）／住所. Suggestions welcomed! Please 特記する／引用する the page's URL, "SheepdogGuides.com/fdb/fdb9JoinRel.htm".
Page has been 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. It passes in some important ways, but still needs work to fully 会合，会う HTML 5 期待s. (Copy your page's URL to your clipboard before clicking on the icon, so you can easily paste it into the validator when it has 負担d.)-->
AND it has been 実験（する）d with...
Why is there a script or hidden graphic on this page? I have my web-traffic 監視するd for me by eXTReMe tracker. They 申し込む／申し出 a 解放する／自由な tracker. If you want to try one, check out their 場所／位置. Neither my webpages nor my programs 会社にする／組み込む spyware, but if the page has Google 道具s, they also 伴う／関わる scripts. Why do I について言及する the scripts? Be sure you know all you need to about spyware.
. . . . . P a g e . . . E n d s . . . . .