|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
Bookmark this on Delicious
Recommend to StumbleUpon
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 ソフトウェア, 10/12.
Often in database work, I find that if you concentrate on what the database is designed to do, rather than what you want, you make 利益／興味ing 進歩.
Take for example the "機能（する）／行事s" (普通の／平均（する）, sum, count, 最小限, etc) which are tantalizingly 示すd if you look at the "機能（する）／行事s" 列／漕ぐ／騒動 of a query design.
In this essay, I am going to show you those 機能（する）／行事s in 活動／戦闘. Once you have learned the 能力s 供給するd they 供給する, you may start realizing things that you now want to do with a database... and even have some idea of how to do them!
To return to my thought of "concentrate on what it is designed to do..."....
For a moment, try not to think too much about what you would use the 機能（する）／行事s and 配合 道具s for. Just concentrate on "What can the database ソフトウェア do?" It is very 平易な to let your mind drift, and imagine that the ソフトウェア will do things you might want it to do, even though it doesn't do that, and thus distract yourself from what you are supposed to be learning about what it 現実に can do.
Continuing with that. Suppose you were learning about carpentry, and the 指導者 was talking about what a 大打撃を与える can do. If your mind wanders, and you start thinking about screws, before long, you'll be imagining 運動ing screws with the 大打撃を与える.
As ever, a little grist for the mill will be helpful.
For this tutorial, I went off to Wikipedia and collected some data about towns in the US. I 収穫d 記録，記録的な／記録するs for every town in Massachusetts, Connecticut, Vermont and New York... every town in those 明言する／公表するs with a 全住民 of more than 29,999, that is.
You can download that database with town 全住民s and a few 逸脱する other facts, zipped up with a ReadMe text とじ込み／提出する.
If you do it on 26 Oct 12, it may 井戸／弁護士席 be incomplete, as I am still 令状ing this tutoria1!... but the basic （米）棚上げする／（英）提議する is already there.
Also in the database... very strange... is a （米）棚上げする／（英）提議する called "Subset". It is a clone of part of the larger （米）棚上げする／（英）提議する. You would not 普通は have such a （米）棚上げする／（英）提議する in a database. If you 手配中の，お尋ね者 the subset, you would 生成する it with a query... but it ふさわしい my 目的s to have it 利用できる. さもなければ, the 人物／姿／数字s and （米）棚上げする／（英）提議するs in this essay would have become much too long. The subset 名簿（に載せる）／表（にあげる）s all of the towns with 全住民s between 29,999 and 40,000. (By the way... in some 状況s, SQL (and thus Open Office's database) use "between" to mean "between and 含むing". I don't.)
Here's a part of the （米）棚上げする／（英）提議する... a subset of "subset", in fact! (All towns in the four 明言する／公表するs with 全住民s (2010 国勢（人口）調査) between 29,000 and 33,000....
明言する／公表する ID Pop Town
ny 86 32850 Rome
ny 87 32736 Poughkeepsie
ma 66 32112 Randolph
ma 67 31915 Watertown
ma 68 31635 Franklin
ny 88 31568 North Tonawanda
ma 69 31531 Falmouth
ma 70 31394 Lexington
ny 89 31146 Jamestown
ny 90 30014 Ithaca
That's the sort of data we will work with. What can we do with it?
This tutorial isn't in the "Level 3" group for nothing! I've had a 失望させるing several hours just roughing it out for you. There are things that don't やめる make sense to me.
It must also be said that what follows has more rough 辛勝する／優位s and loose ends than I like to leave in one of my "published" tutorials. I hope that you will...
1) read it with some patience... no one's 軍隊ing you, after all,
2) not 裁判官 all of my work by the 基準s you find here,
3) But, 非，不，無-the-いっそう少なく 利益 from it! If only for ideas 誘発するd!
It certainly won't give you "all the answers", nor even, I 嫌疑者，容疑者／疑う, 100% 権利 "answers"!
Food for thought, and 誘惑s to try things, at least, though, I hope!
"配合" is a LITTLE like sorting. If I were to group the above by 明言する／公表する, I would get the に引き続いて, where the "===" lines have been put in by me by 手渡す to draw your attention to the groups the data has been gathered into. (Neither VT nor CT have towns in this size 禁止（する）d.)
明言する／公表する ID Pop Town
==== Group of MA towns ============
ma 66 32112 Randolph
ma 67 31915 Watertown
ma 68 31635 Franklin
ma 69 31531 Falmouth
ma 70 31394 Lexington
==== Group of NY towns ============
ny 86 32850 Rome
ny 87 32736 Poughkeepsie
ny 88 31568 North Tonawanda
ny 89 31146 Jamestown
ny 90 30014 Ithaca
The database ソフトウェア also lets us create groups within groups. Let's do that with the same towns, breaking up each group into 部類s based on thousands of 居住（者）s...
明言する／公表する ID Pop Town
==== Group of MA towns ============
--- Sub-group: 32xxx
ma 66 32112 Randolph
--- Sub-group: 31xxx
ma 67 31915 Watertown
ma 68 31635 Franklin
ma 69 31531 Falmouth
ma 70 31394 Lexington
==== Group of NY towns ============
--- Sub-group: 32xxx
ny 86 32850 Rome
ny 87 32736 Poughkeepsie
--- Sub-group: 31xxx
ny 88 31568 North Tonawanda
ny 89 31146 Jamestown
ny 90 30014 Ithaca
How we do that, we'll come to in a moment. But first, we can now look ahead to what the 機能（する）／行事s are for. In the （米）棚上げする／（英）提議するs above, now that the 記録，記録的な／記録するs have been grouped, you can make the に引き続いて sorts of 観察. (Some of the examples are 緊張するd... I'll 演説（する）／住所 that in a moment.)
There are four cities in MA with between 30,999 and 32,000 居住（者）s. The 普通の／平均（する） 全住民 of 32xxx cities in NW is 32,793 The biggest town in MA with いっそう少なく than 32,000 people has 31,915
You've just seen examples of the 機能（する）／行事s "count", "普通の／平均（する）" and "最大限". (There are more to play with, of course.)
As I said, some of those examples are 緊張するd. However, if you were 適用するing the same 道具s to different data, things like "the 最大限 field value 設立する in this group" would be 利益／興味ing.
And, to finish off this section, one little bit of good news. You deserve a reward by now, don't you think? The good news is that you don't always have to group 記録，記録的な／記録するs ーするために use a 機能（する）／行事. You could, for instance, have the simple total 全住民 of all the towns. (I'll show you how to get this. The query is called "queryTotalOfAll". (It has been written to total the town 全住民s in the "Subset" （米）棚上げする／（英）提議する.) I've also 含むd a 報告（する）／憶測 in the database which 報告（する）／憶測s the same （警察などへの）密告，告訴（状）, with a little "stuff" 追加するd, and the 贈呈 tweaked. The 報告（する）／憶測 is called "repTotalOfAll"
For this essay, we are only going to look at 配合 in queries. I believe 配合 is possible in other 状況s, in particular in 報告（する）／憶測s... or am I just remembering that a 報告（する）／憶測 can be based on a query which is doing some 配合? Certainly that sort of 報告（する）／憶測 is possible... I'll show you two!
We will now make a query which will look at the 記録，記録的な／記録するs in the （米）棚上げする／（英）提議する "Subset". You'd use the same techniques if looking at the larger （米）棚上げする／（英）提議する.
You can use either the new query wizard, or the "Create Query In Design 見解（をとる）" 選択. In any 事例／患者, you will 結局 be working in the Design 見解（をとる）, as that is how you edit a query, to get it be "just 権利". For creating a （米）棚上げする／（英）提議する, I think the wizard is more trouble than it is 価値（がある）. But the wizards can, いつかs, be helpful "手渡す 持つ／拘留するing" for the beginner.
We'll create a query which will group the 記録，記録的な／記録するs by what's in the "明言する／公表する" field. It will also 追加する up the 全住民s of the towns, group by group. We'll start the query with the wizard.
Just before we 始める，決める into that...
It would be nice, maybe, to be able to create the に引き続いて result...
明言する／公表する ID Pop Town
ct 15 39559 Shelton
ct 16 36383 Torrington
Total for CT: 75942 ========
ma 54 39880 Holyoke
ma 55 39502 Beverly
ma 56 38499 Marlborough
ma 57 38120 Woburn
ma 58 37819 Amherst
ma 59 35744 Braintree
ma 60 35608 Shrewsbury
ma 61 35177 Chelsea
ma 62 34032 Dartmouth
ma 63 33802 Chelmsford
ma 64 33201 Andover
ma 65 33006 Natick
ma 66 32112 Randolph
ma 67 31915 Watertown
ma 68 31635 Franklin
ma 69 31531 Falmouth
ma 70 31394 Lexington
Total for MA: 592977 ========
ny 85 35462 Long Beach
ny 86 32850 Rome
ny 87 32736 Poughkeepsie
ny 88 31568 North Tonawanda
ny 89 31146 Jamestown
ny 90 30014 Ithaca
Total for NY: 193776 ========
Open Office can give you such a 報告（する）／憶測... but not with a simple query! A query returns a （米）棚上げする／（英）提議する. In a （米）棚上げする／（英）提議する, all 列／漕ぐ／騒動s and columns are "equal".... you can't have "special" 列／漕ぐ／騒動s like the ones with the totals for each 明言する／公表する. (井戸／弁護士席, you can have one "special 列／漕ぐ／騒動" at the 最高の，を越す, if you want to consider the 列／漕ぐ／騒動 with the labels for the columns as part of the （米）棚上げする／（英）提議する- resulting- from- the- query. But it isn't really part of the （米）棚上げする／（英）提議する. It is 単に labels for the （米）棚上げする／（英）提議する's columns.
Part way though the query wizard (step 4), we are going to be asked what sort of query we want to make. We are going to make a "要約 Query". The result will be....
明言する／公表する Pop
ct 75942
ma 592977
ny 193776
(The result will be, as it must for any query, a simple （米）棚上げする／（英）提議する... One 列／漕ぐ／騒動 per result of 追加するing the 全住民s of the towns in a group. First column: 明言する／公表する's 指名する; second column: total 全住民 of the towns.)
Because we want to "do things" with our groups of 記録，記録的な／記録するs, we have to give up, here, seeing the individual 記録，記録的な／記録するs used to 決定する each result. In this 事例／患者, to 決定する each sub-total.
While we will often, for other 目的s, want to see the individual 記録，記録的な／記録するs, we can't, if we want to use the 機能（する）／行事s.
We can show the individual 記録，記録的な／記録するs, if we don't use the 機能（する）／行事s. For that we make a "詳細（に述べる）d query"... but it doesn't 許す 配合. (Although you can use sorting, to get almost the same result.)
So... to create the 要約 of 全住民 totals, 明言する／公表する by 明言する／公表する...
Invoke "Use Wizard to Create Query"
Step 1: Tell the wizard that you want to use （米）棚上げする／（英）提議する "Subset". Put fields "Pop" and "明言する／公表する" in the "Fields in Query" 名簿（に載せる）／表（にあげる）. Those are the only ones we're using. Leave "ID" and "Town" out, or you will have problems. You can try to 始める，決める the order of the columns in the resulting （米）棚上げする／（英）提議する by the に引き続いて... but it may not work. If it doesn't, you can 直す／買収する，八百長をする things in the query design window by 配列し直すing the columns. Either select "明言する／公表する" first, and then "Pop", or use the "up" and "負かす／撃墜する" buttons to put the fields in that order in the "Fields in Query" 名簿（に載せる）／表（にあげる） after both are there.
Step 2: We don't NEED to 課す any sorting, but you may want to sort the results by "明言する／公表する". There's no point in sorting by "Pop", because we will not be seeing individual 記録，記録的な／記録するs.
Step 3: Search 条件s: 非，不，無. That isn't to say you would never have any, if setting up a "要約" query. We're just skipping that extra 複雑化 today.
Step 4: Type of query? We're making a "要約" query. Because we're making a 要約 query, we have to tell the wizard which field to use to group the 記録，記録的な／記録するs. Choose "明言する／公表する". At the same time, although I was trying to separate out the "配合" and the "using 機能（する）／行事s", 明示する that you want to use the "get the sum of" 機能（する）／行事. (It does make sense that the wizard would ask for that here. There's no need to use 配合 in a query if you aren't going to 適用する a 機能（する）／行事. As I said... when making a "詳細（に述べる）d" query, you can "group" 記録，記録的な／記録するs, but you 単に sort them. Our brains will perceive "groups", but the ソフトウェア will only see order.)
Step 5, "Group"??? At this point, step 5 is greed out. When, from step 4's page, you click "next", you will go 直接／まっすぐに to step 7. Our query does 伴う／関わる 配合... but the sort of 配合 that is 伴う／関わるd has already been 暗黙に communicated to the ソフトウェア by the choices we've made. 特に, we have "chosen" to group the 記録，記録的な／記録するs by 明言する／公表する. We will get one line in the results （米）棚上げする／（英）提議する for all of the 記録，記録的な／記録するs 伴う／関わるing CT, one line for all 記録，記録的な／記録するs 伴う／関わるing MA, etc.)
Step 7: 偽名，通称s: This step 許すs us to 決定する the column headings. Each column is associated with a field, and there's a 提案するd 長，率いるing, 偽名，通称, for that field already filled in. You can change the headings. In this instance, it makes sense to change the 長，率いるing for the column associated with Subset.Pop to "Total 全住民 of 中央の-sized towns in 明言する／公表する". (If you agree that "中央の-size" is a reasonable description for "towns of between 29,999 and 40,000 souls."
Step 8: Overview: After you give the query a good 指名する, I used "queryPopSummary" just click "Finish"... but don't be alarmed! Our result is imperfect. の近くに it. 権利-click on the query just created. Click on "Edit", and you will have the query up for editing.
In the "明言する／公表する" column, in the lower part of the design window, the box for "明白な" is not ticked. 追加する a tick. Run the query again, within the design 道具, using the icon in the toolbar. (Or the menu: Edit/Run query. (Or F5!)). You'll see the 改訂するd result at the 最高の，を越す of the design 道具 window.
If the columns in the result from the query were not in the order you 手配中の，お尋ね者, you can 配列し直す them just by dragging the plain gry rectangle just above the "Field" 列／漕ぐ／騒動 of any column in the editor 陳列する，発揮する.
In the database you can download, you'll find a 報告（する）／憶測 called reportTotalOfAll. It is very little more than the results of the query we just created... but the result is 現在のd in a "wrapper" with some text explaining what is in the （米）棚上げする／（英）提議する at the heart of the 報告（する）／憶測. While I am a 広大な／多数の／重要な fan of the 報告（する）／憶測 建設業者 追加する-on, for something simple like repTotalOfAll, you don't need it.
Here's how I created repTotalOfAll...
Invoke the 報告（する）／憶測 wizard.
Step 1: Select the query we just made, queryPopSummary, and tell the wizard to use all of the fields of the query in the 報告（する）／憶測.
Step 2: The default labels will be 罰金. We can alter them later, anyway.
Step 3: 配合: Tell the wizard to group by the data in the "明言する／公表する" field.
Step 4: It would probably be 同様に to sort the results by "明言する／公表する".
Step 5: Layout. I just used the default.
Step 6: Be sure the 指名する the 報告（する）／憶測 will have is 満足な. I changed the default, made it "reportTotalsByState". The プロの／賛成のs and 反対／詐欺s of "static" vs "dynamic" 報告（する）／憶測s are discussed in a different tutorial on my 場所／位置. For now, elect "dynamic".
公式文書，認める... when you go into "edit 報告（する）／憶測", you may think that you're 取引，協定ing with a "mere" OpenOffice wordprocessor 文書. You can 追加する bits, as I have, "around" the （米）棚上げする／（英）提議する.... and this can be important. Making changes to how the data in the （米）棚上げする／（英）提議する is 現在のd is not for the faint hearted! To 配列し直す the order of columns, you can.... 挿入する an (empty) column. Select a whole 存在するing column, copy it, and paste it to the empty column you created, and then 削除する the 不正に placed 初めの. More than that is a story for another day! (I have written tutorials about 報告（する）／憶測 世代 for you. This 報告（する）／憶測 was just to whet your appetite, and make it （疑いを）晴らす that the query need not be the ultimate 製品.)
That 贈呈 gets, perhaps, a bit "over the 最高の，を越す" for a simple little （米）棚上げする／（英）提議する of the 全住民s of the 中央の-sized towns in each 明言する／公表する. Though I 港／避難所't time to go into 詳細（に述べる）s here, in the .zip とじ込み／提出する you will find a form called formPopByState which embeds the results of the query, 現在のing them in yet another manner.
I don't know about you... but I am exhausted.... and out of time.
I'm afraid that the 詳細（に述べる）s of producing...
明言する／公表する ID Pop Town
==== Group of MA towns ============
--- Sub-group: 32xxx
ma 66 32112 Randolph
--- Sub-group: 31xxx
ma 67 31915 Watertown
ma 68 31635 Franklin
ma 69 31531 Falmouth
ma 70 31394 Lexington
==== Group of NY towns ============
--- Sub-group: 32xxx
ny 86 32850 Rome
ny 87 32736 Poughkeepsie
--- Sub-group: 31xxx
ny 88 31568 North Tonawanda
ny 89 31146 Jamestown
ny 90 30014 Ithaca
... will have to wait until another time. What we will need to do is to create an intermediary （米）棚上げする／（英）提議する....
明言する／公表する ID Pop 禁止（する）d Town
ny 86 32850 32 Rome
ny 87 32736 32 Poughkeepsie
ma 66 32112 32 Randolph
ma 67 31915 31 Watertown
ma 68 31635 31 Franklin
ny 88 31568 31 North Tonawanda
ma 69 31531 31 Falmouth
ma 70 31394 31 Lexington
ny 89 31146 31 Jamestown
ny 90 30014 30 Ithaca.... etc
... and then "work our 配合 魔法" on that. Should be simple... 権利? Sigh.
Again... no time to を取り引きする this 適切に, but to whet your appetite, "奮起させる you"....
The に引き続いて shows the design of a query which can produce the results showing at the 最高の，を越す. It is from a 在庫／株 支配（する）／統制する database. The "Inv" （米）棚上げする／（英）提議する 名簿（に載せる）／表（にあげる）s one invoice per 記録，記録的な／記録する. The "Sup" （米）棚上げする／（英）提議する 名簿（に載せる）／表（にあげる）s one 供給者 per 記録，記録的な／記録する. The query 一覧表にするs how many invoices are 現在の from each 供給者. I.e., によれば what we see at the 最高の，を越す of the query design window, there were 4 invoices in the database from 供給者 "kw1sot", and one invoice from each of the other four 供給者s.
So! Sorry to leave you with loose ends, but I hope the 旅行 was still 価値（がある） it? I should thank....
http://searchenterpriselinux.techtarget.com/tip/Turning-data-into-（警察などへの）密告，告訴（状）-with-機能（する）／行事s-in-OpenOfficeorg-Base
... for helping and 奮起させるing me. There is more Good Stuff there!
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 Google+ button code. Sigh.
. . . . . P a g e . . . E n d s . . . . .