|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
Bookmark this on Delicious
Recommend to StumbleUpon
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 ソフトウェア, 2/06-7/15.
I recently had an 予期しない success with something. I have to 自白する that I don't fully understand what is going on (!), but maybe what follows will be of use anyway. Although my example comes from the world of the 株式市場, I'm sure that the techniques have wider 使用／適用.
This tutorial is rather longer than most, but it doesn't "lose the 陰謀（を企てる）"... it just happens to cover a lot of ground! If you are just getting started with ooBase, for now you may prefer to spend your time "knocking 負かす／撃墜する" some of the "low hanging fruit", but 結局 what is in this tutorial will be useful to you. It illustrates some rather neat extraction of data in fields from 多重の （米）棚上げする／（英）提議するs 経由で a query using links creating joins between the fields in the different （米）棚上げする／（英）提議するs. One （米）棚上げする／（英）提議する is even linked to a "master" （米）棚上げする／（英）提議する two different ways!
As I said, this tutorial is not typical of the others on my 場所／位置. Before it gets to the database "how to" 構成要素, it spends やめる a bit of time discussing an area of 株式市場 投資するing, 主要な to a "real world" database 使用／適用 from that 産業. I hope you will find the （警察などへの）密告，告訴（状） on 在庫／株 選択 貿易（する）ing 利益／興味ing in its own 権利, along the way.
The tutorial then takes you through creating two （米）棚上げする／（英）提議するs, with the 見本 data which we will need ーするために 実験（する） that our query with data from 多重の （米）棚上げする／（英）提議するs on it 作品. There is some 構成要素 on why 確かな choices were made in the design of the （米）棚上げする／（英）提議するs. I cannot 強調する／ストレス too much that if you don't choose the 権利 （米）棚上げする／（英）提議するs with the 権利 fields, any database 事業／計画（する） is 厳しく 妥協d from its 手始め.
And then, at last, the tutorial does go into setting up the query! Some discussion of what is going on as the query does its work finished the "main course" of the tutorial. It 結論するs with a little item on creating a calculated field, as "dessert".
A cruel critic might call the tutorial "rambling". I prefer to say that it is more "in depth" than some of my other 試みる／企てるs to help you become more fluent with ooBase.
You can download a copy of final form of the database. 詳細（に述べる）s at end of tutorial.
First a little 解説，博覧会 of some 株式市場 things, which I hope you will find fun and 利益／興味ing, even if you aren't an 投資家.
If you make the 権利 choices, buying and selling 株 you make money. If you fail to do your homework, or misjudge 状況／情勢s, then you give your money to the people who made the 権利 choices. I bought some 株 of Google from someone in September 2005 for $300 per 株. In June 2007, as I am 令状ing this, there are people willing to 支払う／賃金 me $500 for each of those 株. I did 井戸／弁護士席... so far. Should I sell now? Who knows. In six months time we will know what I should have done.
On the other 手渡す, there are the 株 of ESST which I sold to someone else about a year ago for $800. If I had kept them, I could have sold them for $1300 today.
I was 権利 when I said that Google 株 were 価値（がある） more than $300; I was wrong when I said that the ESST 株 price was going to 落ちる.
So far, so 平易な.
There's a more arcane way to 参加する in the 株式市場. For not very much more nuisance than getting yourself in a position to buy and sell 株 as 述べるd above, you can get yourself 始める，決める up to buy and sell "選択s". There are two types that 利益／興味 me: "calls" and "puts". They are 類似の, and I'm about to 述べる both.
What follows is the imperfect understanding of an amateur 投資家. It should not 誘発する you to buy or sell anything. If you are 奮起させるd to go 協議する an 知らせるd teacher, 広大な／多数の／重要な. If the explanation helps you see why I made the database I am going to 述べる, it will have 遂行するd its 目的.
If I buy a call from someone, I have bought the 権利 (we've 調印するd a 契約) to 需要・要求する from him, at a time of my choosing, a 確かな number of 株 in a particular company, at an agreed-now price. The only other "新たな展開" is that 選択s "満了する／死ぬ". That 権利 which I've 購入（する）d only lasts for a 直す／買収する，八百長をするd period of time.
The nice people at Muriel Siebert & Co , who know far more about this than I ever will, have put together more （警察などへの）密告，告訴（状） how to 貿易（する） 選択s, by the way, but they changed the link to the 権利 page, so I've only given you their home page. It is probably 価値（がある） digging for the 選択s guide.
But, going 支援する to a basic explanation, just so that you can understand the database work that I did....
So. When you buy a call, you and someone else have entered into an 協定. Let's say you "bought a call" on Google, with a "strike price" of $530, for September 07. On 14 June, 2007, that would have cost you about $1870 for "one 契約". Google was 貿易（する）ing at about $505 per 株 支援する then.
Let me 拡大する on a few things....
"One 契約" covers 100 株. The call 述べるd する権利を与えるs you to 需要・要求する 100 株 at a price of $530 per 株. (If you choose to make that 需要・要求する... and it is your choice... then you will also have to find the $53,000 ($530 x 100), in 新規加入 to the $1870 you paid for the 契約.)
Hopefully, that makes （疑いを）晴らす what "strike price" means? ($530, in this instance.)
In the circumstances I'm discussing, calls (and puts) 満了する／死ぬ at the end of the third Friday in the month, so those September '07 calls 満了する／死ぬ on September 21st.
Why would anyone buy or sell a call? The 販売人 of the 契約 has decided that the price of Google should not rise as far as $530 before then. You think it will go over $530... at least 概略で $18 over the $530.
If he is 権利, you will never 遂行する／発効させる the 選択, i.e. you will never tell him to cough up the 株. (Why would you 支払う／賃金 him $530 for 株 you can buy "in the open market" for いっそう少なく?) And you will have wasted your $1870.
If you are 権利... let's say Google 急に上がるs to $560 per 株... then you will 需要・要求する that the 販売人 配達する 100 株 to you at $530 each. With what you paid for the 選択, they 効果的に cost you $548.70... but as soon as he 配達するs them to you for the 付加 $530 per 株 at the time you 演習 the 選択, you can sell them on at $560 each. $11.30 利益（をあげる） per 株! :-)
So... that's a call. Remember: you can be a 買い手 or a 販売人 of a call.
Puts are 類似の, and not 必須の to the database work, which we will come to in a moment, but let's just have a quick look at puts first.
A put is like a call, except that the direction of the 株 travel is 逆転するd. If I buy a put, then at any time up to the expiry of the put, I can tell the 販売人 "You will buy from me the number of 株 we agreed, at the price we agreed." When I buy a put, I buy the 権利 to "put" something in the 大臣の地位 of the put 販売人. (And some of his money in my pocket in 交流.)
You might buy a put if you owned some 株 and believed that the price might 落ちる はっきりと in the next couple of months, but for some 推論する／理由 didn't want to 簡単に sell the 株 now. The put is like 保険. And like 保険, you 支払う／賃金 "a 賞与金". (It's even called that.) (You can use calls to "insure" yourself, too.)
As I said, you can be the 買い手 or the 販売人 of a put. So! Four 適切な時期s! Buy or sell, a call or a put! I suppose that I should 強調する／ストレス that some things you might do can cost you a lot of money. What if you were the 販売人 of the call on the Google, 述べるd above. Suppose the price goes to $560 before the person you sold the call to decides to 演習 the 選択, and you've done no hedging? (Don't worry what that is... if you don't know, you probably wouldn't have done it, would you?) You're going to have to buy 100 株 of Google at $560 each (You're going to need, albeit 簡潔に, $56,000) And you're going to have to "give" them away for only $53,000. The $1870 you collected earlier is going to be scant なぐさみ. And of course, the Google, theoretically, could go even higher. (Although the 悲観論者 in me says that it won't, as long as I'm 持つ／拘留するing some. Oh 井戸／弁護士席. The $200/ 株 so far isn't bad. Shouldn't complain.)
And now we're almost to the database stuff, but, hang on to your hats...
What if we were to sell some Google $530s and buy some Google $560s? (They'd cost about $10 per 株 today.)
On that day, we would 結局最後にはーなる with a 逮捕する 利益（をあげる） of $870, assuming we do one 契約 (for 100 株) of each.
Now... if the price doesn't go above $530 before September 21st, then you've "won" and you get to keep all of the $870.
If it goes to $531, the person you sold the $530 calls to is going to 演習 those calls. To find the 株 to 配達する will cost you, one way (buy in market) or another (take from your 存在するing holdings, for いっそう少なく than you could have （負債など）支払うd them どこかよそで) $1 per 株. You've still made a 利益（をあげる） of $770, which is nice.... but $870 was nicer!
If the price of Google reaches $560, the bad news is that you are now losing $2730 ($3000-$870)... but that is all you will lose. No 事柄 how high Google's price rises, the call you bought will 供給（する） 株 at $560 to 会合，会う your 義務 to 供給（する） 株 at $530. Pity about the $2730, though. Guess you shouldn't have been so 悲観的な about Google's price. Guess the person who paid you to take the 危険 that it wouldn't go above $530 裁判官d Google's prospects more skillfully.
You find out what puts and calls are 利用できる, and what they would cost, from Yahoo's 財政／金融 場所／位置. Use the "Get 引用するs" button, and once you have a chart on the 審査する, select the "選択s" item in the menu 妨げる／法廷，弁護士業 at the left. Once you have some call and put prices on the 審査する, for different strike prices, to notice that they are all for a given 満期 date. At the 最高の，を越す of the （米）棚上げする／（英）提議する there are links to pages for prices for other 満期 dates.
井戸／弁護士席... that's it. We can move on to the database now. Remember that the comments on buying and selling puts and calls could 含む／封じ込める errors. You should not do any buying or selling based on those comments.
In this tutorial it will be obvious that there are many things that I don't know. One of the things that I do know is that your （米）棚上げする／（英）提議するs are the 創立／基礎 of your database. Get them 権利, and everything else is a lot easier. One of the 調印するs that you have them 権利 is that no datum needs to be entered twice in a （米）棚上げする／（英）提議する. It may appear twice in the database if it is needed to link a 記録，記録的な／記録する in that （米）棚上げする／（英）提議する to one or more 記録，記録的な／記録するs in another （米）棚上げする／（英）提議する. You will get things entered "twice" so that you can link 記録，記録的な／記録するs from different （米）棚上げする／（英）提議するs, but even there, the datum will usually be entered only once in at least one of the （米）棚上げする／（英）提議するs. Take a database 名簿（に載せる）／表（にあげる）ing my sightings of birds. One （米）棚上げする／（英）提議する 名簿（に載せる）／表（にあげる）s all the birds I might see... each bird 存在 名簿（に載せる）／表（にあげる）d once, and in the （米）棚上げする／（英）提議する, an abbreviation for that bird is defined.
The "sightings" （米）棚上げする／（英）提議する would have 記録，記録的な／記録するs for date, time, place... and bird seen. Each sighting would create one 記録，記録的な／記録する.
With those （米）棚上げする／（英）提議するs, I could 名簿（に載せる）／表（にあげる） the birds seen on a given date, or I could 名簿（に載せる）／表（にあげる） the dates a give type of bird was seen.
What that database would NOT have is the birds' 指名するs written out again and again. It would be too much typing, and too 平易な, say, to call something "mallard" in one 記録，記録的な／記録する but "mallard duck" in another. Not to について言及する typos, e.g. "mallrad". As I said, in the sightings （米）棚上げする／（英）提議する, the bird would be identified by a code.
All of that is by way of 準備するing you for something that I'm going to 述べる in a moment, which may seem 半端物 at first.
It is always a good idea to know where you're going!
So,... what do I want from my database about 選択s 貿易（する）ing?
I want to be able to pull up （警察などへの）密告，告訴（状） on "取引，協定s" I could have done, 取引，協定s of the "sell some low-strike-price calls and buy some high-strike-price calls" type.
To make data 入ること／参加（者） 平易な for this discussion, pretend that you would want to 明示する dates with mere numbers... Instead of 説 "選択 取引，協定 done on 18 June 07", we'll say "取引，協定 done on day 4". In the hypothetical 状況／情勢 the 見本 data postulates, we are already in, say, day 6. Something beyond 4, anyway.
If you have your browser window adjusted to give you a 狭くする column for reading this, in general a good idea, I have to ask you to maximize the width for a moment.
I want to see things like.....
Day Company 満了する／死ぬs Strike1 Proceeds Strike2 Cost 2 IBM Oct07 110 2.70 120 0.55 4 GOOG Jan08 510 47.20 550 29.15 2 IBM Oct07 110 2.70 130 0.10 3 IBM Jan08 110 4.60 120 1.52
(Those are 概略で 権利 for 14 June 2007, by the way, although the （米）棚上げする／（英）提議する says they （機の）カム from さまざまな days because my （米）棚上げする／（英）提議するs would typically have （警察などへの）密告，告訴（状） on different days' 貿易（する）ing.)
I'm going to go through the first line, to 明らかにする the column headings' meanings:
The first line says that on day 4, I sold a 契約 for the Oct07 IBM call at $110, which put $270 in my pocket. On the same day, I sold a call for the Oct07 IBM call at $120, which cost me $55. (結局, but it is beyond the 範囲 of this, I want the 報告（する）／憶測 (form? query?) to tell me that my 逮捕する would be $215 ($270-$55)... should be 平易な.)
Now... remember I said I think I'm getting the hang of designing （米）棚上げする／（英）提議するs?
I think what we want for this 演習 is the に引き続いて two （米）棚上げする／（英）提議するs:
First （米）棚上げする／（英）提議する: OptionsPrices.
Fields:
Day, type Integer [INTEGER] Co, (for "COmpany"), type Text[VARCHAR], length 8 Strike, (for strike price), type Decimal[DECIMAL], places 2 満了する／死ぬs, type Text[VARCHAR], length 5 Price, type Decimal[DECIMAL], places 2
A few comments arising:
"満了する／死ぬs": In a real 使用／適用 to do this 職業, you might use the "Date" datatype, so that you could ask questions like "How many days are left before this 選択 満了する／死ぬs". For this tutorial, the extra data 入ること／参加（者） chore wasn't seen as 価値（がある） the 成果／努力.
The two price fields were made type Decimal because this is the type the ooBase wizard uses for such things.
The 最初の／主要な 重要な is made from the combination of the Day, Co, Strike and Expiry fields
見本 data for this （米）棚上げする／（英）提議する:
2 IBM 110 Oct07 2.70 2 IBM 120 Oct07 0.55 4 GOOG 510 Jan08 47.20 4 GOOG 550 Jan08 29.15 2 IBM 130 Oct07 0.10 3 IBM 110 Jan08 4.60 3 IBM 120 Jan08 1.52
Notice the に引き続いて:
The data in the first line of the 生産（高） we want was drawn from the first two 記録，記録的な／記録するs in the OptionsPrices （米）棚上げする／（英）提議する.
Even though we have the Oct07/ 110 選択, at 2.70, in the 生産（高） twice, it is in the OptionsPrices （米）棚上げする／（英）提議する only once.
Here and どこかよそで: CaSe MATters!!!... You can use GOOG or goog, or Goog... but stick with one of them. The same 適用するs to the dates. "Oct07" or "oct07", etc... but not a mixture. ("Goog" and "goog" will be seen as different as, say, "xom" and "ibm".) The 事例／患者 事柄s in 尊敬（する）・点 of the data you enter, and also in 尊敬（する）・点 of the 指名するs you give fields.
To create what I want, the way I want, we need a second （米）棚上げする／（英）提議する. It 名簿（に載せる）／表（にあげる） the 取引，協定s we have done (or considered)....
Second （米）棚上げする／（英）提議する: OptionsPlays
Fields:
索引, type Integer[INTEGER], 始める，決める AutoValue true Day, type Integer [INTEGER] Co, (for "COmpany"), type Text[VARCHAR], length 8 満了する／死ぬs, type Text[VARCHAR], length 5 LoStrike, type Decimal[DECIMAL], places 2 HiStrike, type Decimal[DECIMAL], places 2
The 索引 field is to 供給する a 最初の／主要な 重要な.
見本 data for this （米）棚上げする／（英）提議する... the data that would give rise to our 見本 "願望（する）d 生産（高）":
2 IBM Oct07 110 120 4 GOOG Jan08 510 550 2 IBM Oct07 110 130 3 IBM Jan08 110 120
Don't 行方不明になる the differences between these （米）棚上げする／（英）提議するs. The first just tells you what different things would have cost you on different days. The second is more 複雑にするd. Each 記録，記録的な／記録する 述べるs a 取引，協定 you either did or considered. To keep the example simple, we are assuming that each 記録，記録的な／記録する 述べるs the 購入（する） of just one 契約 and the same of one 契約, and that both will be for the same expiry date... although they will be for different strike prices.
I hope that's （疑いを）晴らす, because I'm going on to 述べる how you can create a query to produce the 生産（高） we 手配中の，お尋ね者. Just one little thing: Notice how we've made two, separate 言及／関連s to the Oct07 IBM at 110? Because of the way we've 始める，決める up the （米）棚上げする／（英）提議するs, there's no danger of that 存在 shown as costing , say, 2.70 in one place, but maybe 7.20 someplace else.
Start a database called OptionPlaysDemo
Build the two （米）棚上げする／（英）提議するs 述べるd, and put the 見本 data in them.
Now we're going to build the thing that pulls together the fields we want into a 選び出す／独身 result （米）棚上げする／（英）提議する. Once we have that, we can look at working with it. Changing the data in the result from the query does alter the 入ること／参加（者） in the underlying （米）棚上げする／（英）提議する. The query is a way to look at what's in the （米）棚上げする／（英）提議する. It is more than something copied from the （米）棚上げする／（英）提議するs. A 報告（する）／憶測, on the other 手渡す, even a dynamic 報告（する）／憶測 doesn't have this "backward 直面するing" 関係 to the underlying （米）棚上げする／（英）提議するs. Data comes out of （米）棚上げする／（英）提議するs, 直接／まっすぐに or through a query, to 居住させる a 報告（する）／憶測, but once created it is an "unattached" ooWriter 十分な of data from the database.
Even if you are 接近ing the （米）棚上げする／（英）提議する through a query through a form, you still make changes in the （米）棚上げする／（英）提議する is you change what you see 経由で the form.
So... moving に向かって the 生産（高） we 手配中の，お尋ね者:
Start a query, using the wizard.
Step 1: From the OptionsPlays （米）棚上げする／（英）提議する, select the everything except the 索引 field. (You may see "OptionsPlays." in 前線 of each 指名する.)
Still in Step 1, (and you can use the 支援する button if you clicked "Next" too soon!) select the Price field from the OptionsPrices （米）棚上げする／（英）提議する for 傾向 in the fields in the query. Now click Next.
Step 2: We don't need to 始める，決める a sorting order. Click Next.
Step 3: We don't need to 始める，決める search 条件s. Click Next.
Step 4: Again, just click Next, which will skip us over steps 5 and 6.
Step 7: We don't need to, but let's 始める，決める make "Company" for OptionsPlays.Co (instead of "Co"), just to watch what happens. (It will give us a more meaningful column 長，率いるing for the "Co" data in our final result.) Click Next.
Step 8: 割り当てる a 指名する to the query. I used OptionsPlaysAndPricesQuery. Make sure "陳列する，発揮する query" is the selected 選択, take a 深い breath (don't be alarmed by what comes out) and click Finish.
Yikes! Twenty eight 記録，記録的な／記録するs! This isn't what we 手配中の，お尋ね者!
What has happened is that we've "sliced and diced" the 記録，記録的な／記録するs, and 名簿（に載せる）／表（にあげる）d every combination of the pieces. Don't worry about it too much. We're going to "直す／買収する，八百長をする" things next. The "sliced and diced" 現象 is discussed in more 詳細（に述べる） in my tutorial about using 関係s.
の近くに the 陳列する，発揮するd query. Re-open it, but for edit.
You should see a （米）棚上げする／（英）提議する at the 底（に届く） of the resulting window, with 列／漕ぐ／騒動s for Field, 偽名，通称, （米）棚上げする／（英）提議する, etc.
Above the （米）棚上げする／（英）提議する, there should be an area for a GUI 結合，連鎖 管理／経営 道具. There should be two 反対するs on the "page"... on labelled "OptionsPlays", one labelled "選択s". (If you don't have that, but maybe have some text like "SELECT "OptionsPlays"."Day" AS "Day"...", then click 見解（をとる） | Switch Design 見解（をとる）...)
We're beginning to get into the area that is "just 魔法" for me. But what I 述べる 作品! But try to think about WHAT is happening, WHY it 作品. I hope you make more 進歩 than I have so far, and that I "get it" soon! (I do have (Decmeber 2009) the beginnings of a しっかり掴む!)
Part of the 推論する／理由 that it was (and up to a point (at December 2012) still is)) "just 魔法" is that I was not （疑いを）晴らす about 関係s and Joins. They are important, and are not the same thing, but the differences blur in my mind, and I hope to help you fight that problem. Any database with 多重の （米）棚上げする／（英）提議するs should have 関係s 始める，決める up in it, and, thankfully, this isn't so very difficult. Joins become important when you start doing, as we are about to, queries pulling data out of 多重の （米）棚上げする／（英）提議するs....
We're in the query design window. To make our query better, we need to work on its joins.
Click "挿入する | 追加する （米）棚上げする／（英）提議する", and use the resulting dialog to 追加する another instance of the OptionsPrices （米）棚上げする／（英）提議する to the GUI area. (The system will have put the first instance of it there.) The new instance will be labelled "OptinosPrices_1". (You can then の近くに the "追加する （米）棚上げする／（英）提議する or Query" dialog window.)
Arrange the three boxes in the order, left to 権利, OptionsPrices, OptionsPlays, OptionsPrices_1. Also make the boxes bigger, if necessary to get rid of scroll 妨げる／法廷，弁護士業s. (And you can change the 高さ of the パネル盤 they appear in, if it would be helpful, just by getting the mouse on the 権利 位置／汚点／見つけ出す (mouse pointer will change) and dragging gently.))
Now we're going to "draw some lines" between things. The lines will define some "joins". I'm not sure that it 事柄s here, but in some 類似の places it does 事柄, so just be on the 安全な 味方する, and draw the lines in the direction given. When done, you should have...
製図／抽選 a line is done the way you would drag something from a to b....
Use that technique to draw lines (create JOINS) between....
OptionsPlays.Day - > OptionsPrices.Day OptionsPlays.Co - > OptionsPrices.Co OptionsPlays.満了する／死ぬs - > OptionsPrices.満了する／死ぬs OptionsPlays.LoStrike - > OptionsPrices.Strike
and
OptionsPlays.Day - > OptionsPrices_1.Day OptionsPlays.Co - > OptionsPrices_1.Co OptionsPlays.満了する／死ぬs - > OptionsPrices_1.満了する／死ぬs OptionsPlays.HiStrike - > OptionsPrices_1.Strike
Run the query again... OR use the "run query" button on the Query Design window's toolbar. (You're in the Query Design window. The "run query" button is 示すd with two forms with a green tick in 前線 of them. Get the 権利 one, and a new window opens in the Query Design window, showing you what the query returns. (Don't click the one with the red x without taking your heart 薬／医学 first... it 削除するs most of your work. "Edit | Undo" from the menu will 回復する what you have, if you 港／避難所't panicked and done to many other things. (Ctrl-Z doesn't work, by the way.)
"Ah!..." (I hope you're 説) "... that's more like it." Look closely... it's not EXACTLY what we want... a column is 行方不明の, and the order is wrong... but it's の近くに.
(Do click the "save" button from time to time, as with any 計算するing work.)
We need to 追加する a column to the query by 供給（する）ing our 必要物／必要条件s in a column of the （米）棚上げする／（英）提議する at the 底（に届く） of the window. Click on the first empty "（米）棚上げする／（英）提議する" 独房 to the 権利 of a used 独房. Select the OptionsPrices_1 （米）棚上げする／（英）提議する.
In the Field 独房 above this, select "Price" (you may need to use the listbox's scrollbar to see it.)
The "明白な" box should have ticked itself.
Run the query again. The first line should read...
2 IBM Oct07 110 120 2.70 0.55
This is pretty good! The query 選ぶd up....
From a 記録，記録的な／記録する of the OptionsPlays （米）棚上げする／（英）提議する:
The play we made on day 2, with IBM, when we sold a call at 110, and bought one at 120. Look in the OptionsPlayed （米）棚上げする／（英）提議する and find that 記録，記録的な／記録する. Okay? But! We also used the OptionsPrices （米）棚上げする／（英）提議する to look up the fact that the "Oct07 IBM for 110" sold at 2.70 on day three, and the "Oct07 IBM for 120" sold at 0.55 on day three. 冷静な／正味の!
Make the 偽名，通称 for the OptionsPrices.Price field "Price of LoStrike", and make the 偽名，通称 for the OptionsPrices_1.Price field "Price of HiStrike".
=================
関係s and Joins: As soon as your databases have more than one （米）棚上げする／（英）提議する... which shouldn't take long... you really, really せねばならない start setting "関係s" in the database. And before long, you will need "joins". They are not the same thing, but the differences 絶えず blur in my mind, and I hope to help you fight that problem.
=================
It would make better sense, I think, if the fields were in the order.....
Day, Co, 満了する／死ぬs, LoStrike, PriceOfLo, HiStrike, PriceOfHi.
Nothing could be simpler... when you know how.
In the Query Design Window, just put your mouse pointer in the grey rectangle in the unlabeled 列／漕ぐ／騒動 above the "Field" 列／漕ぐ／騒動, and drag the columns left or 権利. You even get a helpful little arrow to give you 信用／信任!
But some of it was more by luck than design.
It seems that something made the OptionsPlays （米）棚上げする／（英）提議する "king". Our final （米）棚上げする／（英）提議する had one 列／漕ぐ／騒動 for each 列／漕ぐ／騒動 in the OptionsPlays （米）棚上げする／（英）提議する. Why not one 列／漕ぐ／騒動 for each 列／漕ぐ／騒動 in the OptionsPrices （米）棚上げする／（英）提議する? Was it because it was an OptionsPlays field 占領するd the first column of the design grid?
Within each 列／漕ぐ／騒動, there were two prices 選ぶd from 記録，記録的な／記録するs in the OptionsPrices （米）棚上げする／（英）提議する. I think what's going on is the に引き続いて. I know it is the links which are responsible, but I also know I have a lot to learn about links. More anon. But first:
The 世代 of the query proceeds a line at a time.
The system 選ぶs up one 記録，記録的な／記録する from the OptionsPlays （米）棚上げする／（英）提議する, the "king" （米）棚上げする／（英）提議する. Then, because of the links, it looks in OptionsPrices a first time, looking for 記録，記録的な／記録するs there with the same values in OptionsPrices.Day, Co, 満了する／死ぬs, and Strike as in, それぞれ, OptionsPlays.Day, Co, 満了する／死ぬs, LoStrike. It finds just one, because of the nature of our data. (I believe that in other circumstances, it might find several, but that would 提起する／ポーズをとる no problem... it would just result in several 列／漕ぐ／騒動s in the query results.) The "魔法" bit is that the 列／漕ぐ／騒動 設立する becomes 利用できる as the source of a field (or fields) in the answer query. We only used one of them... but 公式文書，認める: It was a field NOT 伴う／関わるd in any link. The link seems to 行為／法令／行動する as a filter, but a filter that returns a different 始める，決める of results with each line from the "king" （米）棚上げする／（英）提議する.
The system その上の looked to see if it could find 記録，記録的な／記録するs, again in OptionsPrices, where OptionsPrices.Day, Co, 満了する／死ぬs, and Strike matched, それぞれ, OptionsPlays.Day, Co, 満了する／死ぬs, HiStrike. And again we had a 記録，記録的な／記録する... a different 記録，記録的な／記録する... from which we could use fields... any fields.
Think you half understand? 権利-click on one of the lines in the GUI link designer. Click on "Edit". We may half understand the inner join that we've made. Anyone want to try to 追加する 権利 joins and left joins to what we understand. And how, 正確に／まさに, are links and 関係s connected. (They are... but how?) And did you know that you can define 関係s either at the level of the database （米）棚上げする／（英）提議するs, or within the queries? And within, for all I know, 報告（する）／憶測s and maybe even forms?
Oh... and if that isn't enough fun, use the menu for "見解（をとる） | Switch Design 見解（をとる） On/ Off", and you'll see the SQL for what your query. Just think! If we knew SQL, we wouldn't be at the mercy of the GUI! (Do "見解（をとる） | Switch Design 見解（をとる） On/ Off" again to get the GUI 支援する.)
It's all such a lot of fun! But hey! We got something working.
One last little frill I couldn't resist.
The difference between the proceeds you get for selling a low-strike-price call, and what you spend on the high-strike-price call you buy at the same time is important. Let's get the query to 陳列する，発揮する it!
In the first as-yet-未使用の column to the 権利 of the used columns in the query design grid, put the に引き続いて in the "Field" 列／漕ぐ／騒動...
OptionsPrices.Price-OptionsPrices_1.Price
(I selected "OptionsPrices_1.Price" with the listbox, did Ctrl-A to select all of it, then Ctrl-C twice, to get it twice, then 追加するd the minus 調印する and took out the extra "_1" "by 手渡す".)
Put "Difference" in the 偽名，通称 列／漕ぐ／騒動. Save query. Run query. You should get an extra column, with the difference between the two calculated and 陳列する，発揮するd for you.
By the way... something like this, a value you can calculate from already 現在の fields, is NOT a good thing to 追加する to a （米）棚上げする／（英）提議する as an 付加 field, usually. In 影響, it breaks the "don't enter anything twice" 支配する. Let's look 簡潔に at another example of NOT entering anything twice. Suppose you owned 株 in some companies 完全な, not mere 選択s.
You could have a "holdings" （米）棚上げする／（英）提議する with company 指名する, number of 株, and what you paid for the 株. (You should always 跡をつける that last item carefully... and it is not as 平易な as you might hope.)
Now... "what you paid for the 株". You can either 記録，記録的な／記録する the price per 株, or the price for all of them together, i.e. the price per 株 times the number of 株... but don't 記録，記録的な／記録する both 人物／姿／数字s in the （米）棚上げする／（英）提議する. As long as you have one of them, and know the number of 株, you can always calculate the 行方不明の number. Entering both numbers in the （米）棚上げする／（英）提議する would be an instance of "entering data twice"... which often ends in 涙／ほころびs.
If you would like, you can download a copy of the database, but it would be better to work through the tutorial, to be sure you really understand the 関連した 技術s.
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
. . . . . P a g e . . . E n d s . . . . .