Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org|
このページは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 ソフトウェア, 7/15.
名目上 for someone selling on eBay and アマゾン, but many points of general applicability. It will just be for keeping 跡をつける of money made. Both online markets give 販売人s good 在庫／株 跡をつけるing 道具s.
You can download the "finished" database, "FDB021.odb" ("解放する／自由な Data Base, example 21")... but I would recommend ALSO "building" it, step by step, as you read the tutorial. I think you will be amazed a the wealth of 詳細（に述べる）s which come to your attention, if you do.
The 使用者 will enter a 記録，記録的な／記録する for each sale made. From time to time, small 新規加入s will be needed to a （米）棚上げする／（英）提議する 記録，記録的な／記録するing what 税金s are 徴収するd by さまざまな 明言する／公表するs. As often they wish, 使用者s will run two 報告（する）／憶測s. One will give 利益（をあげる）s from eBay sales, the other 利益（をあげる）s from アマゾン. Why two? The 支配するs about 料金s are different in the two marketplaces. Although I won't 演説（する）／住所 it in depth here, it would be 平易な enough to make the 報告（する）／憶測 give 利益（をあげる）s for a given 範囲 of dates.
I'll concentrate on the （米）棚上げする／（英）提議するs I 始める，決める up, then the query and 報告（する）／憶測s needed. I hope you will be able to infer some of the whys and wherefores as we go along. You will have to take on 約束 WHY the （米）棚上げする／（英）提議するs are as they are for a bit.
One of the challenges of database 開発 is that you have to start with the （米）棚上げする／（英）提議するs, but what you need in the （米）棚上げする／（英）提議するs is 決定するd by what you want to 達成する with your 報告（する）／憶測s. You have to DESIGN from the "報告（する）／憶測" end, but DEVELOP from the （米）棚上げする／（英）提議する end.
Many things can be done 異なって... you might want to put the price in as dollars and fractions of dollars, instead of as pennies, for instance. But do it my way while working through the tutorial, if you want The 平易な Life. THEN do your 見解／翻訳／版, for your wants. This is just a STARTING POINT for your own database. One thing I have left out: The 販売人's cost in the goods sold. 追加するing this would be trivial. Just another field in Sale, and another 称する，呼ぶ／期間／用語 in the 計算／見積りs. (I didn't want to clutter this with "詳細（に述べる）s".)
In all of the に引き続いて, by the way, things are often 事例／患者 極度の慎重さを要する. If I say call a field "Price", don't use "price"... if you want a 静かな life.
Main （米）棚上げする／（英）提議する... "Sale"
SaleID: 最初の／主要な 重要な, unique identifier made up of the date of the invoice, yymdd (5 and always 5 characters. Oct, Nov, Dec as a,b,c), 加える a letter, to 許す up to 26 sales per day. E.g. 15b072 for the second sale of 7th November 2015. That 判型 will seem 半端物 to many. It really does work very 井戸／弁護士席, has many virtues.
Price:... in pennies. Before 地位，任命する and packing. Before 税金s. And we are going to base all of this on the 前提 that the 料金 告発（する），告訴（する）／料金d to the 販売人 by the marketplace is "hidden" from the 買い手.
TaxAu, for "税金 当局", data type, Text(直す／買収する，八百長をする), length:2: This field will have 入ること／参加（者）s like "NY", "CT", "nn". The first two are US 明言する／公表するs, where the 物品税s 変化させる from 明言する／公表する to 明言する／公表する. The last is for "no 物品税 payable on this". The values in this field will have to be 現在の in the "TaxPayable" （米）棚上げする／（英）提議する, which we will come to in a moment.
Mkt, for Marketplace, i.e. eBay or アマゾン: "e" for eBay, "a" for アマゾン. I 港／避難所't done it, by the （米）棚上げする／（英）提議する should be 始める，決める up to REQUIRE an 入ること／参加（者）, and REQUIRE "e" or "a" here. (限界ing the input to a 範囲 of values IS 論証するd in the 事例／患者 of the TaxAu field.
PP, for 地位，任命する and packing. Again: In pennies.
This won't have many 入ること／参加（者）s in it.
TaxAuID- 最初の／主要な 重要な: See 公式文書，認める above about Sale.TaxAu. Also data type Text(直す／買収する，八百長をする), length:2
TRa- 税金 率. Enter 12 for a 12% 税金.
Those are my （米）棚上げする／（英）提議するs. If I've got them 権利, the 残り／休憩（する） will be "平易な".
First a simple (ha!) 関係...
の近くに all the （米）棚上げする／（英）提議するs, but not the database. From the main 事業／計画（する） 管理／経営 window, select "道具s/関係s"
追加する the "Sale" and "TaxRate" （米）棚上げする／（英）提議するs to the workspace.
Put mouse pointer on Sale.TaxAu. 圧力（をかける） and 持つ／拘留する left mouse button. Drag (nothing will move) pointer over to TaxRate.TaxAuID. 解放（する） mouse button. You may want to drag one of the little boxes standing for each （米）棚上げする／（英）提議する to a new position. When things are nice, you should see a line between Sale.TaxAu and TaxRate.TaxAuID, with "n" at the Sale end, "1" at the TaxRate end.
SAVE THE RELATIONSHIP!
You have just said that you don't want 入ること／参加（者）s in the Sale.TaxAu, unless the 入ること／参加（者） matches an 入ること／参加（者） in TaxRate.TaxAuID. The "1" says that for a given value, e.g. "NY", you will only see it ONCE... in the TaxRate （米）棚上げする／（英）提議する.
Play with the （米）棚上げする／（英）提議するs... try to enter some data. Be sure to "始める，決める" any data you enter into TaxRate before trying to 追加する a 記録，記録的な／記録する in Sale which depends on it. That is to say here's what you do if you have a sale to PA to 記録，記録的な／記録する, and you 港／避難所't put PA into the TaxRate （米）棚上げする／（英）提議する yet. I am going to 教える you to do it "wrong", so that you can see what happens in something that I often do, even to this day, and which can have you scratching your 長，率いる.
Go to the TaxRate （米）棚上げする／（英）提議する.
Enter a 記録，記録的な／記録する for PA, but, for now, DON'T do more than...
Enter PA in the first field, 6 in the second field. After typing the 6, just do nothing more in TaxRate.
Use your mouse to go 支援する to the Sale （米）棚上げする／（英）提議する.
You'll get an "正直さ 違反" error when you try to leave the 記録，記録的な／記録する, after you have "entered" it in the Sale （米）棚上げする／（英）提議する. 現実に... you 港／避難所't entered it. You have only STARTED to enter it. Same thing with your PA 記録，記録的な／記録する in TaxRate. Click "Ok" in the error message to make it go away. Go 支援する to the TaxRate （米）棚上げする／（英）提議する. Click on a line OTHER than the "PA" line. NOW your 入ること／参加（者） has (fully) gone into the （米）棚上げする／（英）提議する.
Go 支援する to the Sale （米）棚上げする／（英）提議する. You will find that NOW you CAN leave the line with the sale to PA in it.
Good! We've got out （米）棚上げする／（英）提議するs. Enter some data, or just content yourself with the data 供給（する）d in the download.
供給する at least....
Sale... 157181 5000 PA e 100 157182 1000 NY a 100 ---- TaxRate... PA 5 NY 16
Now... USING the data!....
Three steps...
a) Create a basic query. Queries pull data from one or more （米）棚上げする／（英）提議するs, and create a "一時的な", "invisible", "inside the computer" （米）棚上げする／（英）提議する. THAT （米）棚上げする／（英）提議する will be the input for a 報告（する）／憶測 we will create in a bit. It is also where the Really Clever stuff happens.
b) Create queries on the queries!
c) Create 報告（する）／憶測s.
About 20% though the に引き続いて, you may lose the will to carry on. The good news is that this is by far the worst part of this 事業／計画（する）. The "queries on queries" are 平易な, and the 報告（する）／憶測s REALLY 平易な.
It may console you in your 悲惨 to remember that while I was 令状ing this, I somehow lost my query, and had to re-令状 it from scratch. Happily, these 公式文書，認めるs were done, to follow. Whew.
I INITIALLY created query with the wizard. Pulled in...
All fields from the Sale （米）棚上げする／（英）提議する TaxRate.TRa
Use the wizard's defaults for all other 面s of the （米）棚上げする／（英）提議する, up to the 指名する it is to be saved under. Save it as SaleDataForProceeds.
Now, from ooBase main 事業／計画（する） 経営者／支配人 window, 権利 click on the query, open it for editing.
You should get a "two pane" type window, rather like the one we used to 始める，決める up the 関係. But this is DIFFERENT!
The "two forms with a green tick" button will run it. Click that. You should now have a three pane window... three 水平の 禁止（する）d, rather like the 旗 of Spain (without the crest!) You may have to adjust their vertical widths by dragging at the 境界s.
A 広大な number of 記録，記録的な／記録するs in the result, because, 概して speaking, you get everything 多重の times, covering all possible combinations.
In the 禁止（する）d with little boxes showing the fields of the two （米）棚上げする／（英）提議するs, as we did when setting up 関係s, create a line from TaxRate.TaxAuID to Sale.TaxAu by dragging.. Your line won't have the "n" and "1" we saw before.
Run the query again, and you should get a sensible result...
SaleID Price TaxAu Mkt PP TRa 157181 5000 PA e 100 6 157182 10000 NY a 100 16
In another, not too hard to reach, シナリオ, you would have been given NO 記録，記録的な／記録するs! Oops! But, again... we WOULD BE 進歩!
In the other シナリオ, which 事柄s to you because you may "go there" one day: First too many 記録，記録的な／記録するs, now too few. Sigh.
I can't really explain it, I 港／避難所't got the words.
(BIG brownie points to anyone who emails to tell me where THAT line comes from!)
We have created a "join" for our query to use. In OUR 事例／患者, it is already of the 権利 sort. I will now show you how to tweak it, make it the RIGHT sort of join, for the day when you need that.
The join, by the way, doesn't, by the way, say or 施行する anything about the data in the （米）棚上げする／（英）提議するs. It is 簡単に a part of the query, part of the 支配するs for what will be put into the 一時的な （米）棚上げする／（英）提議する the query produces.
権利 click on the line 代表するing the join between Sale.TaxAu and TaxRate.TaxAuID.
Select "Edit".
You will, I 推定する／予想する, see that you 現在／一般に have a natural inner join. Good! That's what we need. Another time, it might not already be selected for you, and I'm not sure of the 権利 指名する for the join you want... but there is helpful text at the 底（に届く） of the Join 所有物／資産／財産s dialog. In our simple 事例／患者, for the "inner" type join, the text says...
含むs only 記録，記録的な／記録するs for which the contents of the 関係のある fields of both （米）棚上げする／（英）提議するs are 同一の.
Leave the "Fields 伴う／関わるd" ALONE, but
Leave the "Natural" box UNticked.
In a (わずかに) more 複雑にするd シナリオ, the message at the 底（に届く） for what we want would be....
含む／封じ込めるs ALL 記録，記録的な／記録するs from （米）棚上げする／（英）提議する "Sale", but only 記録，記録的な／記録するs from （米）棚上げする／（英）提議する "TaxAuID" where the values in the 関係のある fields are matching.
This, as I say, I can't 適切に explain, but what I half understand from the text just given is at the heart of it.
Click "取り消す" to get out of looking at the join 所有物／資産／財産s dialog, or "Ok" to 完全にする the edit of the link, if you are 調査するing the 影響s of different choices.
If you have made any, save the changes to the query.
Run the query again. You should get still a sensible result! (Or get one now, if you have 前進するd into the コンビナート／複合体 circumstances.
What is a sensible result??...
You saw one earlier, I hope. It will look like a （米）棚上げする／（英）提議する. (It IS a （米）棚上げする／（英）提議する, but not in every way that you may assume.)
It will have the に引き続いて fields. They should seem familiar....
SaleID Price TaxAu Mkt PP TRa
Looking at what we have...
As I said, the （米）棚上げする／（英）提議する looks unremarkable, at first ちらりと見ること. But think about it...
The first five columns are 陳列する，発揮するing what's in the Sale （米）棚上げする／（英）提議する. Good! We need to know about our sales. But think about the last column, think about where the TRa value in each 記録，記録的な／記録する has come from. THIS is CLEVER! In the （米）棚上げする／（英）提議する 組み立てる／集結するd by the query, the TRa value for each line is a number fetched from the TaxRate （米）棚上げする／（英）提議する, the RIGHT number to go with whatever TaxAu was 明示するd in the 記録，記録的な／記録する in the Sale （米）棚上げする／（英）提議する.
Don't worry if you don't see WHY that is 冷静な／正味の. Read on. WHAT it is good for will be 十分な.
We've made a start. But we need to 追加する another column (at least). This one will be even more "魔法" than the ones so far.
First we need to take a moment to look in 詳細（に述べる） at the way the marketplaces 告発（する），告訴（する）／料金 for their services. I should 追加する that what I am going to 明言する／公表する here as "the way" is NOT やむを得ず EXACTLY what アマゾン or eBay do. Even if it were, they could change it. But what I will 述べる COULD be their 支配するs, and will show you the 原則s of putting together the 報告（する）／憶測s, so that you can adapt the examples to your 現在の needs.
Let's say that you only sell 調書をとる／予約するs on アマゾン, and that they (アマゾン) always 追加するs $6.00 ("600" in the 部隊s of the database) to the "price", collects the sum of your price 加える the $6.00 from the 顧客, and then passes on to you that, minus a flat 料金 of $5.00. (This, with different numbers, is what they did for a long time. Only 飛行機で行く in the ointment? The 量 they 追加するd for p&p was insufficient to cover the actual costs to the 販売人. In some 事例／患者s I lost money when I sold a 調書をとる／予約する.) Under those 支配するs, you don't need to enter a lot of the data you need to enter for the eBay sales. In fact, for an アマゾン sale, you only need to enter a SaleID and a price! If only everything were so simple! (You only have to enter those two to find out how much you will receive from the sale. Why do you care what the 顧客 would have to 支払う／賃金?)
Let's say that for an eBay sale, they 告発（する），告訴（する）／料金 you a パーセント of (Price+税金+PP). This will be messy. Sigh. Life is messy. But we can do it.
A 詳細（に述べる）: For now, the パーセント will be hard-coded into the query. Changing it will be a 事柄 of changing the query. Not ロケット／急騰する science, but it would be so much nicer... and I KNOW it CAN be done... if you could 簡単に put the パーセント into a small (one 記録，記録的な／記録する) （米）棚上げする／（英）提議する, and the query would fetch the number from there. Even nicer, but it would be a lot more work... what if the パーセント changes half way through the year, and you want 利益（をあげる）s for the year? Under my 天然のまま answer, 現在のd here, you'd have to run two 報告（する）／憶測s, one for the part of the year with the first 率, and a second for the other part of the year. If the "eBay パーセント" （米）棚上げする／（英）提議する also had an "up to this date" field, you COULD... with やめる a lot of work, I 嫌疑者，容疑者／疑う, have just one 報告（する）／憶測, and it would 適用する the 権利 パーセント to each 処理／取引.
支援する to our "simple" answer....
We're going to 追加する two columns to the （米）棚上げする／（英）提議する the query produces. One will be "Proceeds By アマゾン 支配するs", the other "Proceeds by eBay 支配するs". Then we'll make two 報告（する）／憶測s, one to 一覧表にする proceeds from アマゾン sales, the other for the other.
What we are doing is very like what I explained in my tutorial "Calculated Fields in the OO database". If this tutorial is giving you a 頭痛, maybe give that one a try, for (almost) the same techniques, in a わずかに simpler シナリオ.
Still in the query editor, in the 底（に届く） pane, where you have 多重の columns for the fields in the （米）棚上げする／（英）提議する produced by the query, you need to 追加する what I will explain in a moment.
Take a second to get your bearings. Usually, fields are the ROWS (水平の) in a （米）棚上げする／（英）提議する. Here it is one field to a COLUMN (vertical). But we can do this! We're computer people!
For a gentle start, not that it is 価値（がある） MUCH, click on the first empty 独房 in the "Field" 列／漕ぐ／騒動. Enter Price+3. (If, as I hope, you entered "Price" as the 指名する of the field in the Sale （米）棚上げする／（英）提議する, you enter "Price" here. If you used "price", use "price" here. The 入ること／参加（者） is 事例／患者 極度の慎重さを要する, in other 作品.) Don't be alarmed, or fight it, if Base 追加するs 引用するs around the word Price before long. Save the query. Run it. The （米）棚上げする／（英）提議する that results should have 伸び（る）d a column, with 5003 and 10003 in the two 列／漕ぐ／騒動s for my デモ data.
Now we will tweak the start we've made.
追加する ProcAm as 偽名，通称 for the field we're working on.(For "PROCeeds from sale by AMazon 支配するs"). Don't worry about the GeekQuotient of that 指名する. 使用者s won't see it, and it is good for our wants.
By the way: It will seem 半端物, but it is the only way to our goal that I know: We will calculate what our proceeds WOULD be, by BOTH marketplaces' 支配するs for each sale. Of course, only one of them, in each 事例／患者 is of any use to us in the long run.
Go 支援する to the "Field" field (!) for the column we've just 追加するd.
We said that アマゾン gives the 販売人 the price the 調書をとる／予約する sold for, 除外するing 税金, 除外するing p&, i.e. the number in our "sold", MINUS a 逮捕する $1.00 ("100").
So change the 決まり文句／製法 in the column we are working on to "Price"+100.
平易な! And reasonably "real world"... if you 追加する in at least one column to the Sale （米）棚上げする／（英）提議する, and do what's necessary to 会社にする／組み込む what's in it. The column would be "cost of goods+p&p expenses". (If it were me, I would 分裂（する） those out into TWO columns, one for each.) As 現在のd, our database tells us what money we get from アマゾン and eBay, who both take their 料金s at source... we never see them. But it doesn't take away from our 欠陥d "proceeds" 人物／姿／数字s our OTHER costs. As I said... 供給するing for those is trivial, and was only left out of this to 減ずる clutter.
Save and run the query again, and you should see good "Would get from アマゾン" numbers.
There's nothing "new" in what we need to do for this. It is just a little more コンビナート／複合体 in the 詳細（に述べる）s of the 決まり文句／製法 because of the 支配するs we said eBay 適用するs.
A 詳細（に述べる）: Under eBay, WE decide how much p&p is collected from the 顧客, on our に代わって.
Start another column. Call it ProcEB, and, just to get it started, again make the field "Price"+3. Save your changes. See that you get what you should...
SaleID Price TaxAu Mkt PP TRa ProcAm ProcEB 157181 5000 PA e 100 6 5100 5003 157182 10000 NY a 100 16 10100 10003
(By the way: the alignment of the data won't be as above. But don't fuss with it. 使用者s... and before long you... won't be seeing the data in the （米）棚上げする／（英）提議する in this form.)
That's the "hard" stuff done. 井戸／弁護士席. Intellectually hard. Now we have to fuss with the 詳細（に述べる）s of the 決まり文句／製法 for what eBay will send you.
We said they would 追加する the price, the p&p together. Taking our sale in PA for an example, that gives us 5100. Then 追加する the 関連した 税金. 6%.... IF the goods are SENT to an 演説（する）／住所 in PA. (Something the database doesn't 現在／一般に を取り引きする... we're assuming that it always is 追加するd. The way around this is to enter "nn" as the 税金 code for 小包s not going to the 明言する／公表する the 販売人 is in.... which means, I guess, that much of what we've done is unnecessary! A NY 販売人 would need the NY 入ること／参加（者） in the TaxRate （米）棚上げする／（英）提議する, and the "nn" 入ること／参加（者）... and no others! Oh 井戸／弁護士席.)
(Shake my 長，率いる in annoyance, and to （疑いを）晴らす cobwebs. 支援する to what I was 説....)
We had 5100 so far. Assume a sale from PA to PA, and 追加する the 6% that our （米）棚上げする／（英）提議する gives us. (The （米）棚上げする／（英）提議する is still 価値（がある） having, as it makes changing the 率 of 税金 告発（する），告訴（する）／料金d (when it IS 告発（する），告訴（する）／料金d) 平易な.)
That brings us to 5406, the 税金 存在 306*.
Let's say eBay would take 10%. Your proceeds would be 4866 or 4865, depending on how eBay's computers are programmed to 対処する with the fraction of a penny they are 予定.
Remember, we are working on pennies, and we have entered パーセントs not as fractions, but as whole numbers.
I could give you "the 決まり文句／製法"... but I want you to see how you GET the 決まり文句／製法. There are 多重の 大勝するs you could have taken. This is how I got to the result...
First I made the column 陳列する，発揮する the 税金 to be 告発（する），告訴（する）／料金d. Between さまざまな things, that was a little tricky, we are working in pennies, and have entered パーセントs not as fractions, but as whole numbers. (Working 異なって brings on other problems!)
You have to multiply by 100 and then divide by 100 in さまざまな places because, since we decided to work with integers (whole numbers), fractions, if they should arise, are just thrown away.
(You can change the width of the columns in the 底（に届く） pane of the query design window, by the way... just drag them.)
The 決まり文句／製法 you need is....
(("Price"+"PP")*"TRa")/100
YOU DO NOT, by the way, want to put something like this in your main （米）棚上げする／（英）提議するs. That is a thought that occurs to many people. And it 作品. Sort of. For a while. And then you finally 結論する that "the 専門家s" were 権利, and you have to spend hours cutting that stuff OUT of your main （米）棚上げする／（英）提議するs again.
Now we build in another 層. We build up the 決まり文句／製法 to show what the price 加える the 税金 would be. Parentheses, (.....), are your friend, but you have to use them with care. Start by putting all of what you had before inside a pair of parentheses. Then 追加する "Price"+ "PP"+ in 前線 of it. The 決まり文句／製法 becomes...
"Price"+"PP"+((("Price"+"PP")*"TRa")/100)
That should give 5406. At this point, it would be really nice if we could "put" that somewhere, let's call it "SoFar", and could use a 言及／関連 to "SoFar" for what we need next.... a 決まり文句／製法 for what eBay gets. If we could, "next" would 簡単に be...
(SoFar*10)/100
(*10/100, with the parentheses shown.. they can 事柄!... because eBay, we said, takes 10%, and because we aren't doing fractions. (It would be *9/100 if eBay were taking 9%.))
Sadly, I know no way of creating a "SoFar". Happily, although the result is messy to look at... not a trivial 欠陥... heaven help us if there is an error hiding in it... with the computer's 削減（する） and paste, we can create the に引き続いて 比較して easily...
(("Price"+"PP"+((("Price"+"PP")*"TRa")/100))*10)/100
... which should give 540 or 541, depending on how the わずかの penny is dealt with. eBay was 予定 540.6. In this 事例／患者, ooBase returned 541... it 一連の会議、交渉／完成するd, it didn't truncate. More clever than I thought!
Now that we know what eBay will take, we can calculate what we will get from...
"Price"+"PP"-WhatEBayWillTake
Of course, the "WhatEBayWillTake can't be written like that... we have to use the 広大な／多数の／重要な long thing we worked our a moment ago. Start creating the new line by putting parentheses around what we had before, to 避ける "order of 操作／手術s" problems.
(It should come up as 4559, shouldn't it? Always create some 実験（する） data, make sure that the computer gets the same answers, as you go along, as you get with a pencil and paper.)
By the way... にもかかわらず seeing no end of numbers, we 港／避難所't seen the number the 顧客 would 現実に 支払う／賃金, have we? Not if the 顧客 was 支払う／賃金ing 税金 on the 取引，協定. But we don't need that, do we? Not broken out and 陳列する，発揮するd. It was USED in our 計算／見積りs, but not left 明白な in our final result.
WHEW! Who would have thought it could be so tedious? But not, in essence, "複雑にするd". If you take it step by step.
At last we have the main QUERY on which we will build our other queries, on which we will build our REPORT!
(We're DONE with the query, once we get the 報告（する）／憶測 built. Until the 支配するs the marketplaces use when calculating their take change, anyway. But if those 支配するs DO change, we won't need to change the 報告（する）／憶測, or the other queries, when we change the underlying query.)
Use the query wizard again, to start the query....
Step 1: Make sure the "（米）棚上げする／（英）提議する" selected as the basis is SaleDataForProceeds
The ESSENTIAL fields are...
SaleID Mkt ProcEB
(You might want others... Price, maybe?)
Step 2: DON'T 適用する a sort at this point. (We will do the sorting during the 報告（する）／憶測 世代. I THINK it was a sort 適用するd here that got in the way of other things, later.)
Step 3: Search: Use Match Sale...Mkt / is equal to / e
Steps 4-7 (you won't visit them all): Use defaults.
Step 8: Call query "DataForEBayProceeds"; click Finish.
If you put only my two 実験（する） 記録，記録的な／記録するs into Sale, you should see just the 記録，記録的な／記録する for 157181 in the result of running the query. の近くに it.
Repeat the above, with the obvious (I hope!) small differences to create a query called DataForAmazonProceeds
All that is left is creating two simple 報告（する）／憶測s.
The 報告（する）／憶測 we need will not be very "clever". You might want to visit some of my other "make a 報告（する）／憶測 from a query" tutorials, as I am tired, hungry, and short of time here!
As I について言及するd earlier, we are going to create TWO 報告（する）／憶測s... one to 報告（する）／憶測 proceeds from アマゾン sales, one to 報告（する）／憶測 proceeds from eBay sales.
Here we go. We'll do the one for eBay first...
Select "報告（する）／憶測s" in the left 手渡す pane of the ooBase main 事業／計画（する） 経営者／支配人 window.
Click on "Use Wizard to create..."
Make sure that the "（米）棚上げする／（英）提議するs or Queries" pull 負かす／撃墜する has "Query:DataForEBayProceeds" selected.
From the fields on 申し込む／申し出, move to the "Fields in 報告（する）／憶測" column....
SaleID ProcEB
Click "Next" to get to step 2 of the wizard, at least as it was at OO 4.1.1
Change the ProcEB label to "Proceeds before cost of goods and p&p"
In step 3, just click next. (Invoke no 配合.)
Step 4: Sort by SaleID. If you used my 計画／陰謀 for 割り当てるing sale IDs, this will give you the data in chronological order. (I think they would appear in the 権利 order, anyway, as we put a sort order in place with the query... but might 同様に be sure.)
Step 5: Layout: Tabular
Step 6: 肩書を与える "EBay Proceeds", dynamic 報告（する）／憶測, create now.
That will create a good start to a 報告（する）／憶測. It is nothing special. It will LOOK awful.... but does it REALLY 事柄, for instance, that the 量s are left 正当化するd, not 権利 正当化するd? (直す／買収する，八百長をするing that is trivial.)
You will want to tidy up the 報告（する）／憶測's layout14c, make it more elegant. For that I leave you to your wits, or to my other tutorials. Yes...you CAN have it 追加する up the total of all the proceeds.
Before you play with the 報告（する）／憶測 too much, go 支援する to your "Sale" （米）棚上げする／（英）提議する, 追加する more 記録，記録的な／記録するs.
The 報告（する）／憶測 for your アマゾン proceeds is created the same way.
If you want a 報告（する）／憶測 on the proceeds for a given （期間が）わたる of time, you 達成する that by putting 基準 in the 関連した query (DataForEBayProceeds, or DataForAzonProceeds). You can have TWO "SaleID" columns in the query design. Leave "明白な" for one of them un-ticked. Put 基準 like...
>'14c999' <'158000'
...into the query design, and your 報告（する）／憶測 will only 名簿（に載せる）／表（にあげる）, for the example 基準 given, sales from after the end of 2014 until before the start of August 2015.
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 . . . . .