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 the Google+ button code. Sigh.|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
Bookmark this on Delicious
Recommend toStumbleUpon
(Minor 小衝突 up, 02 損なう 17)
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 ソフトウェア, 6/07- 3/17.
In this tutorial you will see how to 始める，決める up a data 入ること／参加（者） form for two 関係のある （米）棚上げする／（英）提議するs. I tried what follows myself again, from scratch, 2/15, OO 見解／翻訳／版 4.0.1, and tried to update any 時代遅れの 構成要素 from 支援する when it was first 草案d.
In 孤立／分離, what we do may see a bit pointless, but...
Although it is not light or lively reading, 令状ing the に引き続いて was even harder than reading it. If you take a 深い breath, and can 軍隊 your way thought all that follows, I believe it will 強化する your database building 技術s. Please do what is needed to make all my work something more than a waste of time?
There is some overlap between the contents of this tutorial and two others I've published, but all of them are talking about important 概念s, and I believe that it can be helpful to look at things from 多重の directions, when trying to master them. (The other tutorials were Getting started with 多重の （米）棚上げする／（英）提議するs, 関係s and "Using 多重の （米）棚上げする／（英）提議するs and relations")
In fact, I've written several tutorials with "関係s" (as in "relational database") at their 核心, and so have produced a sub-menu page for these 関係のある essays.
Part of my difficulty was that, in my mind, two 概念s were not 十分に 際立った. I was blurring the distinction between 関係s and joins, two superficially rather 類似の "linking" 機械装置s. In this essay we talk only of 関係s. (Joins come up when you start building queries (or 報告（する）／憶測s) 製図／抽選 from 多重の （米）棚上げする／（英）提議するs.)
The database used for illustrating what is taught in this tutorial happens to be for managing 株式市場 投資s. 恐れる not! The same 反対するs we use here- （米）棚上げする／（英）提議するs and forms- are used in many 使用／適用s. （米）棚上げする／（英）提議するs are made of fields. Those other 使用／適用s are only different in the 指名するs on the fields, and perhaps the data-type of the field. But whatever the 使用／適用 we are building, we will still be using fields/ （米）棚上げする／（英）提議するs/ forms, etc. (So don't go away, just because you're not doing a 株式市場 使用／適用!(And 許す me for not editing out the repetition of that which arises soon?)
Underlying the example are two （米）棚上げする／（英）提議するs. One 名簿（に載せる）／表（にあげる）s the 指名するs of some 在庫／株s, and the other （米）棚上げする／（英）提議する 名簿（に載せる）／表（にあげる）s 経済的な 部門s into which the 株式市場 can be 分裂（する） up.
With that modest database we will have made a useful start に向かって a 一括 which can 生成する useful （警察などへの）密告，告訴（状） for the 投資家 持つ／拘留するing the 在庫／株s 記録，記録的な／記録するd in the database.
"But I'm not a 株式市場 投資家!" you cry...
Don't worry...
Humor me? Pretend you want to start 投資するing? Just for a while?
You may have come to this tutorial from a longer essay that I'm working on. If you have, you may already have a database called PDB058. If not, create it now, and create the に引き続いて two （米）棚上げする／（英）提議するs. (See my "getting started" tutorial if you want help with "create the database and two （米）棚上げする／（英）提議するs".)
The two （米）棚上げする／（英）提議するs we're going to use should be 始める，決める up as follows. It really helps if you 現実に DO what is 述べるd as we go along. Use my 指名するs, if you do, with 資本／首都 letters and lower 事例／患者 in the same places... and your life に引き続いて the tutorial will be easier.
First （米）棚上げする／（英）提議する: StockNames, consisting of 4 fields:
The 最初の／主要な 重要な for this （米）棚上げする／（英）提議する will be created from a combination of the first two fields. (I.e. it will have a "構内／化合物" 重要な.)
The 指名する of the first field is 単に a 縮めるd 見解／翻訳／版 of "ticker", the 称する，呼ぶ／期間／用語 used in the 財政上の world for an (almost) unambiguous abbreviation of a company's 指名する. You can say "I have 株 in Pfizer", or you can say "I have 株 in PFE".
Tick, type Text(直す／買収する，八百長をする)[CHAR], length 10 Dis, type Text(直す／買収する，八百長をする)[CHAR], length 1 Sect, type Text(直す／買収する，八百長をする)[CHAR], length 3 指名する, type Text[VARCHAR], length 32
(The last field will 持つ／拘留する UP TO 32 characters. Not 決定的な to today's story. Pedantic? Moi?
The 最初の／主要な 重要な for this （米）棚上げする／（英）提議する is a 構内／化合物 重要な, made from the first two fields. (I'll explain what the fields are for in a moment.) If you didn't 始める，決める up the 最初の／主要な 重要な as you created the （米）棚上げする／（英）提議する, just open the （米）棚上げする／（英）提議する for edit, select the first two 列／漕ぐ／騒動s, and put the little 重要な in the gray 独房 of the left 手渡す column with a 権利-click.
You really must have something 指定するd as 最初の／主要な 重要な in anything you do in Open Office. I would guess that a 構内／化合物 重要な, such as we've discussed here is not terribly ありふれた. (Nor rare.) Often, the 最初の／主要な 重要な will be just the contents of one column of the （米）棚上げする／（英）提議する, one 始める，決める of fields. We'll see that configuration in our second （米）棚上げする／（英）提議する.
(Things might seem to "work" for a bit, at first, if you have no 最初の／主要な 重要な... but the 涙／ほころびs will soon begin.)
Just before we move on, a word about the fields in StockNames. The last field (指名する) is the everyday 指名する for the company a given 記録，記録的な／記録する is about. The first field ("Tick") is the tickertape abbreviation for that company, an abbreviation used in many 状況s across the 投資するing world, and carefully managed by the 在庫／株 交流s, so that you have a good chance of finding what you want with nothing more than the ticker code. There is a slight 飛行機で行く in the ointment. Take "S". That was the ticker for Sears & Roebuck. That company is gone. Since at least June 2007, "S" has been used to say "Sprint".
At any one time, only one company is 現在／一般に identified by, say, "S". But in different 時代s, which company is "S" can change.
So... Because we want to use our database not only for 現在の holdings, but for 記録，記録的な／記録するs of past holdings and 処理／取引s, we need a way to DIStinguish between, say, different "S"s. Which is what the "Dis" field is for. We'll put a code there, to distinguish one "S" from another. Sears, might, for instance have "S" in the first field, and "e" in the second. (From SEars). Sprint could have "S" in the first field, and "p" in the second, in the "Dis" field. 公式文書，認める that these codes are not universally agreed.
The second field in StockNames 持つ／拘留するs a "disambiguation" code.
Even if there's no problem like the Sears/ Spring problem, which I just tried to explain, some companies have 多重の classes of 在庫／株, often called "class A" or "class B". For instance, I once own some Hubble Class B. (Hubble has since done away with the different classes, but what was the 事例／患者 still makes a 満足な example:
The ticker for Hubble was "HUB". If my disambiguation code for my Hubble B was "b", then those 株 were 蓄える／店d as tick="HUB" + Dis="b" in my 記録，記録的な／記録するs.
Hubble 貿易（する）d (and still 貿易（する）s) on the NYSE. NYSE 在庫／株s three letter tickers, like "HUB". But いつかs, some places, you saw "HUBB", meaning Company: Hubble; Class: "B".
And it gets worse! Depending on what system you are working in, you use HUBB, HUB.B or HUB-B to ask about Hubble Class B 在庫／株. Pity "the big boys" can't seem to agree on a 基準 way of 取引，協定ing with 多重の classes of a given company's 在庫／株. But that's the reality. を取り引きする it. ("取引，協定ing with things" like this is often an 問題／発行する for database designers, by the way.)
Onward...
Second （米）棚上げする／（英）提議する: CodesSectors. Consists of two fields. ("Sec" in these 指名するs for "安全", i.e. "在庫／株". Not because this is SECond （米）棚上げする／（英）提議する.)
This （米）棚上げする／（英）提議する's 最初の／主要な 重要な is a simple 重要な, based on just the first field. The "PK" below is shorthand for "This field is the the 最初の／主要な 重要な for this （米）棚上げする／（英）提議する.")
SecID, type Text(直す／買収する，八百長をする)[CHAR], length 3, PK SecDescrip, type Text[VARCHAR]), max length 10
For the sake of the tutorial, enter the に引き続いて data. Contrary to general good working practice, just 接近 the （米）棚上げする／（英）提議するs 直接／まっすぐに to put this data in. (In general, you should create a form, and enter data through that.)
A 詳細（に述べる）: It doesn't really 事柄 what 事例／患者 you use when entering tickers. You could use, say, PFE, pfe or Pfe. I've made a considered choice in the 事例／患者 条約s I've 示唆するd, but you don't have to do things as I have... but at least be 一貫した.
StockNames:
PFE a dru Pfizer IBM a tec International 商売／仕事 Machines GOOG a tec Google
CodesSectors:
dru 麻薬s tec 科学（工学）技術
That's a good start!
The 部門 field is the 利益／興味ing one. Before we talk about how that field is built into our database, perhaps I should say what a "部門" is? It's what you probably 推定する／予想する: 投資家s 推定する／予想する companies which do 類似の things to have 類似の 特徴. Two energy 部門 在庫／株s, say BP and Exxon, are likely to have similarities. Mr. Bush takes us to war, and the 株 prices of most energy 部門 在庫／株s go up. At the same time, the 株 price of companies in the 航空機によるs 部門 go 負かす／撃墜する. The 投資家 worries that 燃料 prices will rise, and the 航空機によるs will have trouble raising their prices enough to 持続する their previous 利益（をあげる）s. It is 利益／興味ing that the market assumes that the oil companies will do better if oil becomes harder to 得る. Of course the oil companies are selling oil, and the 航空機によるs are buying it. So: A company's "部門" 示すs the general part of the 経済的な 生態学 the company is part of.
In our database, we have a （米）棚上げする／（英）提議する 名簿（に載せる）／表（にあげる）ing the 指名するs of the 部門s we choose to 分裂（する） everything up into, and the abbreviations we've chosen for those 部門s. We have a field in the StockNames （米）棚上げする／（英）提議する where we will use one of those abbreviations to characterize a given company. This approach will save us a lot of typing, and chances for typos.
What we have done may seem "obvious", but it is at the heart of a big part of what is wonderful about relational databases. What are "relational databases"? The meaning of "relational" is something that you will 徐々に 吸収する as we go along. To get you started: There is a 関係 between our two （米）棚上げする／（英）提議するs, isn't there? The "部門" （警察などへの）密告，告訴（状） in the StockNames （米）棚上げする／（英）提議する 記録，記録的な／記録するs relates to （警察などへの）密告，告訴（状） in the CodesSectors （米）棚上げする／（英）提議する's 記録，記録的な／記録するs. (Many people do, by the way, use "a relational database" without using the features that make it more than a simple, 非，不，無-relational database. Using the extra features is optional... but it brings many 利益s.)
(There's more on 関係s and joins in a short(er) page I created which 会談 about these important 概念s in general 条件. They are not the same thing, but the differences 絶えず blur in my mind, and I hope to help you fight that problem.
Moving on: の近くに any ooBase things you may have open, apart from the main ooBase 事業／計画（する） 管理／経営 window (see next paragraph) and (optionally) the "help" window. But leave "the database" open.
(What's the "main ooBase 事業／計画（する） 経営者／支配人 window"? It has 3 panes: One fills the left 味方する, is 長，率いるd "Database", and 許すs you to select （米）棚上げする／（英）提議するs, Queries, Forms and 報告（する）／憶測s. The other two are one above each other on the 権利, one is 仕事s and the other 名簿（に載せる）／表（にあげる）s the 利用できる （独立の）存在s for whatever part of the database system you are working on. 詳細（に述べる）s 利用できる. Opens in own tab.)
Next, we'll create two forms which can be used for looking at, or editing, the 記録，記録的な／記録するs in the （米）棚上げする／（英）提議するs.
Select "Forms" in the left 手渡す column of the main ooBase 事業／計画（する） 管理／経営 window. Then click on "Use Wizard to Create Form." Don't be alarmed by the OpenOffice Writer page that opens... your "Database Form" will be a fancy ooWriter "文書"! 公式文書，認める that the Wizard's steps are 示すd in its left-手渡す column.
Step 1: Select （米）棚上げする／（英）提議する: CodesSectors, and move both of the 利用できる fields to the "Fields In The Form" パネル盤. (The 平易な way is to click on the ">>"). And Click Next.
Step 2: Don't 始める，決める up a sub-form. Just click next to go on. You will skip over steps 3 and 4, and find yourself at...
Step 5: You want to arrange the data 支配（する）／統制するs as a datasheet. The appropriate 選択 has probably already been made. (You'll see "as datasheet" where it is needed.) And Click Next.
Step 6: Again, what you want is probably already selected: "The form is to 陳列する，発揮する all data". Don't disallow anything. And Click Next.
Step 7: 適用する Styles: Play with this if you must. I just took the defaults. And Click Next.
Step 8: Give it the 指名する CodesSectorsDataEntry; leave the setting on "Work with the form", and click "Finish". (If "next" is not grayed, you've probably made a mistake. In this 事例／患者, click "Next", and you may be taken 支援する to where the problem was first important. 公式文書，認める: That may be after the place where you did what needs changing.)
If all's 井戸／弁護士席, you should now have a form which looks very like the （米）棚上げする／（英）提議する looked when you manipulated it 直接／まっすぐに.
Try 追加するing another 記録，記録的な／記録する:
SecID:ene
Sec:Descrip:Energy
And, for 推論する／理由s which should become （疑いを）晴らす, another...
SecID: mis
SecDescrip: Misc (for "Miscellaneous")
Be sure to leave the 現在の 記録，記録的な／記録する when you have finished filling in all of its fields... as usual. Until you leave the 記録，記録的な／記録する (or use the "Save 記録，記録的な／記録する" toolbar button) your new data is only on the 審査する, not in the database. You've "filled in a form" (sort of), but not sent the data anywhere.
Adjust the size of the window that form is in. Leave it open.
Follow 類似の steps to create a form called StockNamesDataEntry which 陳列する，発揮するs all of the fields of the StockNames （米）棚上げする／（英）提議する.
Hurrah! You're two steps 負かす／撃墜する the road to becoming the next 株式市場 大君!
We have a small database that will 持つ／拘留する the 指名するs of companies, and a little bit of （警察などへの）密告，告訴（状） about them.
Let's make a 審議する／熟考する mistake.
Enter a 記録，記録的な／記録する in the StockNames （米）棚上げする／（英）提議する with...
TEST / a / xxx / TestRecord.
What's this "xxx" 部門? (Companies in the porn 産業 are not, as a 支配する, 名簿（に載せる）／表（にあげる）d on the 在庫／株 交流s.) It is a 実験（する）, to see what happens if we enter "bad" data. All of the 入ること／参加（者）s in the 部門 field should be abbreviations 現在の in the 記録，記録的な／記録するs that 構成する the CodesSectors （米）棚上げする／（英）提議する. Checking that no 明示していない 部門s are in use is a large part of the 推論する／理由 for the CodesSectors （米）棚上げする／（英）提議する. Either the data 入ること／参加（者） 操作者 has mistyped something, or the person who said that the company was in 部門 "xxx" is imagining that a 部門 存在するs for which there has no proper 準備／条項. It isn't hard to "適切に 供給する" for a 部門, even a new 部門, but the system is built in a way that encourages discipline.
At the moment... and we're going to "直す／買収する，八百長をする" this... the system 許すs you to enter the "bad" 部門 "xxx".
(削除する this 実験（する） 記録，記録的な／記録する, to 避ける problems which will さもなければ arise in a moment. (To do this: 権利 click on the rectangle just to the left of "TEST" in the "Tick" column, and then click on the "削除する 列／漕ぐ／騒動s" which you せねばならない see.))
Our database "作品", on a superficial level. However, good programs for managing data 許す you to 始める，決める up 支配するs which 妨げる the 入ること／参加（者） of something like "xxx"... a 部門 abbreviation not defined in the CodesSectors （米）棚上げする／（英）提議する. And we're going to 始める，決める those 支配するs up in a moment.
There's another thing that a good program for managing data will let you 始める，決める up: Something to stop you, say, 削除するing the "dru / 麻薬s" 記録，記録的な／記録する from the CodesSectors （米）棚上げする／（英）提議する as long as there are any 記録，記録的な／記録するs in the StockNames （米）棚上げする／（英）提議する which use that code. "Referential 正直さ" is the 指名する for what is 確実にするd by such 支配するs.
の近くに anything that is open, apart from the main ooBase 事業／計画（する） 管理／経営 window and (optionally) the help window.
On the menu 妨げる／法廷，弁護士業 of the main ooBase 事業／計画（する） 管理／経営 window, click 道具s | 関係s. The "Relation design" window should open.
Use the "追加する （米）棚上げする／（英）提議するs" window to 追加する, one after the other, StockNames and CodeSectors to the main "Relation Design" window.
Arrange the 代表s of the （米）棚上げする／（英）提議するs so that StockNames' is to the left of CodesSectors'.
Before we go その上の: A little （警察などへの）密告，告訴（状）. If you see "CodesSectors.SecID", that is just an efficient way of 説 "the SecID field of the CodesSectors （米）棚上げする／（英）提議する".
Put your mouse pointer in the middle of "Sect" (in StockNames). Depress, and keep depressed, the left mouse button. Move the pointer to the middle of "SecID" in CodesSectors. 解放（する） the mouse button. (It is as if you were trying to drag "Sect" の上に "SecID".)
Be sure you drag from StockNames.Sect to CodesSectors.SecID, or you will get a 複雑にするd dialog to を取り引きする, and it is 平易な to fluff the necessary settings. (Bring it up, have a look at it... but 削除する any 関係 that arises, and re-do it by dragging in the 権利 direction. When you drag in the 権利 direction, a line should appear between the two field 指名するs, with "1" at one end, and "n" at the other. (More on these labels in a moment.)
Get an error message? You will if you forgot to 削除する the TestRecord 記録，記録的な／記録する, 部門 "xxx", as you were told to above. The system won't let you 始める，決める up a 関係 if 存在するing data 侵害する／違反するs the "支配する" 設立するd by the 関係. Finding the 感情を害する／違反するing data can be tiresome. Thus, it is best to 始める，決める up your 関係s 早期に in the database's 開発. If you have, bad data doesn't get in, so you don't have to find it, take it out!
許す a little digression? I hope so....
Once you have things 始める，決める up, there's a "gotcha" that still gets me. Suppose you're working with the database we're discussing here. You've had it "done" for a while, you're just filling it with data. And you want to 追加する a 在庫／株 from a 部門 you 港／避難所't used before. Let's say the 在庫／株 is BIDU, and you want to define a 部門 called "ifs" (InFormation Services), and you 港／避難所't entered any 在庫／株s from this 部門 before.
You can't enter the 在庫／株 until you've made an 入ること／参加（者） in the CodesSectors （米）棚上げする／（英）提議する. 罰金. You make that 入ること／参加（者）. Then you go 支援する to the StockNames （米）棚上げする／（英）提議する, and try to enter BIDU. It seems happy, but you can't leave the line! Either the system just 辞退するs, or an error message pops up.
What's going on?
Probably the に引き続いて....
After you entered the "ifs / （警察などへの）密告，告訴（状） Services" 記録，記録的な／記録する into CodesSectors, did you use your mouse or cursor to move to a different 記録，記録的な／記録する? If you didn't, the new 記録，記録的な／記録する is still 単に on your 審査する, not yet "in" the database. Even if you were only editing an 存在するing 記録，記録的な／記録する, until you either click "Save 現在の 記録，記録的な／記録する", or 簡単に move to a different 記録，記録的な／記録する (my usual practice) the new data is not "in" the database! Thus, when you went over to the StockNames （米）棚上げする／（英）提議する, tried to enter the BIDU 記録，記録的な／記録する, the database would not 受託する it, because it didn't yet "know" about the ifs 部門.
I still make the mistake of failing to move out of a 記録，記録的な／記録する after changing it... but I do 認める the symptoms arising pretty quickly these days, and it is 平易な enough to go 支援する and do what needs to be done. So I suppose I am learning something. I just wish I didn't learn so slowly. Sigh. End of 転換!
After you've done the things I told you to before I started the 転換, you should see a line between the 代表s of the two （米）棚上げする／（英）提議するs. (Move the （米）棚上げする／（英）提議するs around. See how it can make the line sensible? I think that the "rubber banding" 手続きs built into the GUI are pretty neat!)
At the left 手渡す end, you'll see a little "n", and at the 権利 手渡す end a "1". The line says that there is a "one- to- many" 関係 between CodesSectors.SecID and StockNames.Sect.
"One- to- many?" you may be asking.....
It means that any given value for the field will be 設立する in only one 記録，記録的な／記録する in the CodesSectors （米）棚上げする／（英）提議する, but there may be many, any number ("n") of, 記録，記録的な／記録するs in the other （米）棚上げする／（英）提議する where that value appears.
Think about it. It would be silly to have a given 部門 code stand for more than one 部門, but there are many companies in the same 部門, so the 部門 code in many of the company 指名するs' 記録，記録的な／記録するs will, for example, be "ene".
If a field is a （米）棚上げする／（英）提議する's 最初の／主要な 重要な, you cannot enter the same data in two 記録，記録的な／記録するs OF THAT TABLE. That 保護するs us from inadvertently creating a new 部門 which re-uses a code which we've already 配分するd to another 部門. We cannot, say, make an 入ること／参加（者） in CodesSectors like "ele / electric 公共事業（料金）／有用性s" if we already have "ele / electronics". The program for managing our data is giving us 保護 against something we might do by 事故. BUT: (don't let this fact 混乱させる you) You CAN have "ele" in many of the 記録，記録的な／記録するs in the StockNames （米）棚上げする／（英）提議する. In THAT （米）棚上げする／（英）提議する, the "ele" isn't going into a field that is part of the （米）棚上げする／（英）提議する's 最初の／主要な 重要な. (It is simple, really. You will "get it"... 結局. And for a while after you think you understand, you will trip over 存在 混乱させるd, and after a bit of that you will really understand it! It is just the nature of database work. Are you 堅い enough to "get there"?)
以前, we could enter "bad data" in the Stocknames （米）棚上げする／（英）提議する. We could enter "TEST / a / xxx / TestRecord". (This would be bad because there should no 部門 with "xxx" as its code.)
の近くに the "Relation Design" window.
Re-open the StockNamesDataEntry form (or the StockNames （米）棚上げする／（英）提議する... but you wouldn't 普通は work 直接／まっすぐに with that, would you?)
Try entering "TEST / a / xxx / TestRecord". It will let you enter that... but as soon as you try to leave the 記録，記録的な／記録する, ooBase will complain, as it should, 警報ing you to the fact that you are trying to enter bad data. ooBase puts it more 正式に: "Error 挿入するing new 記録，記録的な／記録する: 正直さ 強制 違反"... I.e., the 正直さ of your data would be gone if this 記録，記録的な／記録する became part of the （米）棚上げする／（英）提議する. Change the "xxx" to a code that IS 現在の in the CodesSectors （米）棚上げする／（英）提議する, and the new 記録，記録的な／記録する will be 受託するd. Brilliant! This is Really Clever. Don't let your by- now- glazed 注目する，もくろむs fail to notice how marvelous this is.
I hope you remember that we created a 部門 called Misc, code "mis"? This was so that we can always enter a new 記録，記録的な／記録する in the StockNames （米）棚上げする／（英）提議する, even when we aren't sure what 部門 to use to characterize the company. We just say, for the moment, that it is in the "mis" 部門. From time to time, we would probably ask ooBase to 名簿（に載せる）／表（にあげる） all companies in the "mis" 部門, and we'd try to 割り当てる at least some of them to a more meaningful 部門. (It is 平易な to ask ooBase to show just the "mis" companies.) If we 手配中の，お尋ね者 to put them in a not- yet- 供給するd- for 部門, we could... we just have to go to the CodesSectors （米）棚上げする／（英）提議する first, create the new 部門 and 割り当てる its abbreviation, and then we can change any company's 部門 code to the new 部門.
A few 半端物s and ends....
To 引用する the ooBase help とじ込み／提出する: "If the Relation Design window is open, the selected （米）棚上げする／（英）提議するs cannot be 修正するd, even in （米）棚上げする／（英）提議する Design 方式. This 確実にするs that （米）棚上げする／（英）提議するs are not changed while the relations are 存在 created."
What I just 引用するd shouldn't come as a surprise, if you think about it. Don't give ooBase too much to 対処する with. If you are working on setting up 関係s, it would probably be best if the （米）棚上げする／（英）提議するs were の近くにd. And 副／悪徳行為 見解／翻訳／版. Do one thing at a time. It shouldn't 意味ありげに cramp your style.
A 詳細（に述べる）: You can edit the 外見 of the forms. You don't need to, so skip past this if it doesn't come easily.
の近くに anything that is open apart from the main ooBase 事業／計画（する） 管理／経営 window and (optionally) the help window.
Click on "Forms" in the 事業／計画（する） 経営者／支配人's left 手渡す pane; 権利 click on "StockNamesDataEntry", select "Edit". Your form will open in ooWriter, because the form is "just" a (コンビナート／複合体) ooWriter "文書". Now we get to the tricky bit. Click somewhere along an 辛勝する／優位 of the （米）棚上げする／（英）提議する (Tick/Dis/Sect/指名する) which is an 反対する within the form. What's tricky is clicking in the 権利 位置／汚点／見つけ出す. If you get the 権利 位置／汚点／見つけ出す, you will select the （米）棚上げする／（英）提議する, which will be shown by the fact that it now has little green squares at its corners, and in the middle of each 味方する. If you drag these, you can re-size and reposition the （米）棚上げする／（英）提議する on the form. You can also resize the whole window. Save what you've done and の近くに the window. I know that your changes to the （米）棚上げする／（英）提議する's position and size will be saved. I think that the 明言する／公表する of the window when you の近くにd it will be saved. Now use the ooBase 事業／計画（する） 経営者／支配人 to open the form 普通は, i.e. for mere data 入ること／参加（者）. (Do this by 二塁打-clicking on it's 指名する.) （米）棚上げする／（英）提議する a better size? I hope so! As I said... if not, don't worry about it.
I had my form open for data 入ること／参加（者）, not form editing, and managed to get things in a 絡まる. I had some 列／漕ぐ／騒動s that I didn't want, and 権利 clicking didn't bring up the "削除する 列／漕ぐ／騒動?" 選択. I just の近くにd and re-opened the （米）棚上げする／（英）提議する, and all was 井戸／弁護士席. I'd been 開始 and の近くにing all sorts of things, any one of which could have made the （米）棚上げする／（英）提議する "令状 only". (A controllable "令状 only" 選択 is probably 利用できる. It would be useful, for instance, in a 在庫／株 支配（する）／統制する program where you 手配中の，お尋ね者 junior 従業員s to be able to enter data, but not 除去する it.)
I have every 信用／信任 that during normal 操作／手術s you won't get into the 絡まる I was in. And it was 平易な to get out of, in any 事例／患者.
By the way: The "read only" that you see in the window's 肩書を与える 妨げる／法廷，弁護士業 doesn't mean that you can't 追加する or 除去する 記録，記録的な／記録するs to the database. It means that you can't (at this point) alter the form you are using to edit the data.
Remember why we hoped that ooBase 会社にする／組み込むd referential 正直さ 道具s? What happens, say, if we try to 削除する the "dru / 麻薬s" 記録，記録的な／記録する from the CodesSectors （米）棚上げする／（英）提議する while we have a 記録，記録的な／記録する in the StocksNames （米）棚上げする／（英）提議する consisting of "PFE / a / dru / Pfizer"? Try it! Hurrah! ooBase says, in more コンビナート／複合体 条件, "No, won't.".
This may all seem コンビナート／複合体, 乾燥した，日照りの, unnecessary. Take my word for it: It is wonderful, and using the 道具s 現在のd in this tutorial will 支払う／賃金 （株主への）配当s. For a little 事業／計画（する） like a 名簿（に載せる）／表（にあげる） of telephone numbers, you are ありそうもない to have any need of these 道具s. But if you want to go その上の with database design, these 道具s will be part of what you need. With them, you create 強健な, reliable, efficient databases.
I've written several tutorials with "関係s" (as in "relational database") at their 核心, and so have produced a sub-menu page for these 関係のある essays.
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.)
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 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. Mostly passes. There were two "unknown せいにするs" in the Google+ button code. Sigh.
. . . . . P a g e . . . E n d s . . . . .