Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
This 事例／患者 熟考する／考慮する is ーするつもりであるd to 改善する your database 技術s. If you are working with ooBase, the 解放する／自由な Open Office database, the "do this" 指示／教授／教育s should work perfectly for you. Even if you do not have ooBase (why not?), the 事例／患者 熟考する／考慮するs are 十分な of general 原則s which will 適用する to any database work.
I hope you someday find that ooBase delights you as much as it has me. There's more about it in the main 索引 to this 構成要素.
Remember that Open Office, 含むing Base, is 解放する／自由な! And it is 伸び（る）ing traction. It's not new. Big 会社／団体s and 政府 団体／死体s are 可決する・採択するing it as their 基準 office 控訴... and saving million$. 令状 your elected 代表者／国会議員s today, ask them why they 支払う／賃金 Microsoft for a wordprocessor.
This page is suppose to be "browser friendly". Make your browser window as wide as you want it. The text will flow nicely for you. It is easier to read if your window is not too wide.
Page contents © TK Boyd, Sheepdog ソフトウェア ®, 3/06.
A number of charities 毎年 receive 出資／貢献s from me. (Not least Wikipedia, my computer-philic friends!)
Before I started the database which is the 支配する of this 事例／患者 熟考する／考慮する, I had a sheet of paper with a 列／漕ぐ／騒動 for each charity, a column for each year. I give to each charity once a year. The order of the charities on that 名簿（に載せる）／表（にあげる） is not alphabetical, it just 反映するs the historical 事故s of when I began giving to each.
I want to continue using that 一致する of my giving, but I also want a "copy" of the （警察などへの）密告，告訴（状） in my computer. From time to time, I start a new "署名／調印する on paper" 一致する, and I also need an 年次の 名簿（に載せる）／表（にあげる） of 寄付s, preferably in alphabetical order by the charity's 指名するs
I'm going to solve this problem "不正に" in the first instance. Some of the shortcomings of the method I'll use do not have too many too terrible consequences in the very small database that I am 建設するing.
The "worst" thing that I am going to do is to have 多重の fields for "money given". There will be one for gift in 2006, gift in 2007, gift in 2008, etc.
This is "bad" on two counts.
a) It is not as easily 延長するd as the better system which I hope to 令状 up as a sequel to this 事例／患者 熟考する／考慮する. Let's say I 始める，決める things up with fields for every year through 2009. In 2010, I will have to 追加する extra fields. Not a 抱擁する chore... but one that can be 避けるd.
b) Unless I give to every charity every year, the （米）棚上げする／（英）提議する will have "穴を開けるs" in it. A charity that is 追加するd to the 名簿（に載せる）／表（にあげる） of those I give to in, say, 2007, will have empty fields for the earlier years. A charity that is dropped from the 名簿（に載せる）／表（にあげる） of those I give to in, say, 2005 will have empty fields in the later years.
The "reward" that has tempted me to use this "bad" design is that the form for data 入ること／参加（者） will be やめる 平易な to use. It will be almost like filling the （警察などへの）密告，告訴（状） in on a spreadsheet.
I 嫌疑者，容疑者／疑う that 親族 緩和する of 世代 of the 報告（する）／憶測 for a year's giving, under the two approaches to 蓄える／店ing the data, will be "six of one/ half dozen of the other". That is to say that while some 面s of doing the 報告（する）／憶測 will be 平易な with the "不正に 始める，決める up" database that follows will be easier than doing the 報告（する）／憶測 from the 井戸／弁護士席 designed database, others will be hard.
In designing databases, always think about how 井戸／弁護士席 your design 与える／捧げるs to 確実にするing that your data is 訂正する. The design discussed in this 事例／患者 熟考する／考慮する does have the virtue of closely matching the "署名／調印する on paper" 記録，記録的な／記録するs it depends upon, thus eschewing some possible sources of 混乱. Perhaps I should have said earlier that I tend to 避ける working 直接／まっすぐに on a computer. They let me 負かす／撃墜する too often. I will sit with my checkbook, charity requests, and "署名／調印する on paper" 一致する. As I 令状 checks, I will make an 入ること／参加（者） in the 一致する. Then I will enter the 人物／姿／数字s from the 一致する into the computer, and use it to look at さまざまな things and 準備する the 年次の 名簿（に載せる）／表（にあげる） of gifts. The database will really come into it's own when my 現在の "署名／調印する on paper" 一致する becomes too 十分な, too marred by alterations. I will then create a new sheet to be the starting point of the next "署名／調印する on paper" 一致する. It will have the past few years' (but not all 事前の years') gifts 名簿（に載せる）／表（にあげる）d. Charities I've stopped supporting will be left off. New ones will have proper places in the 名簿（に載せる）／表（にあげる）, instead of 存在 squeezed in, or relegated to the 底（に届く）.
First I created a folder for the database and all associated 文書s. In this 事例／患者, the folder is called PDB059, as it is my 59th database in a series that started when I was using Paradox. The folder 指名する will probably not arise again in this tutorial, but be sure that you keep the things on your disk 組織するd. If you can't find things, they are of no use to you! It also helps you keep 支援する-ups 首尾よく.
The database will have just one （米）棚上げする／（英）提議する: Gifts
It will have the に引き続いて fields, に引き続いて types and sizes. All of the "text" fields are of the "Text [varchar]" variety.
the G2005, G2005, G2005, etc fields are all of type integer. They are for my gifts of 2005, 2006, 2007, etc. I will always give a whole number of dollars, e.g. $30, never $29.95, so I might 同様に use the simple data type.
見本 data....
Let's say that my 署名／調印する-on-paper 一致する looks like.....
CHARITY 2005 2006 ------- ---- ---- Frontier Nursing 100 120 Americares 100 120 Technoserve 120 Mayo Clinic 500 500 Pomfret School 100 120 Wikipedia 50 50 アマゾン 医療の 事業／計画（する） 100 100
These are all good and worthy charities, by the way.
The data for the not-obvious fields of the database would be as follows. The "MySortOrder" values given ふりをする how Technoserve would have been slotted in if it was not in the 名簿（に載せる）／表（にあげる） in 2005 when the first MySortOrder codes were 配分するd.
ChariID ChariShortName MySortOrder ------- -------------- ----------- frnu Frontier Nursing aa amca Americares bb tese Technoserve bg macl Mayo Clinic cc irc I'nat'l 救助（する） Cttee dd wiki Wikipedia ee amme アマゾン 医療の 事業／計画（する） ff
(A little point: I 指名するd the Charity ID field "ChariID" to keep it short. If you give a long 指名する to a field that will have short 入ること／参加（者）s, you may be annoyed with yourself later when designing a tabular form which needs a wide column just for the 長，率いるing! Ordinarily I would have given "MySortOrder" a shorter 指名する, but as it was a いっそう少なく-than-obvious field, I thought I'd leave the 指名する longer and more meaningful for you. 公式文書，認める my aversion to upper 事例／患者 letters. It 害（を与える）s readability (bad) but 簡単にするs data 入ること／参加（者） for me, a poor typist. 公式文書，認める that there is a method in the madness of the assignment of ChariID codes. The 支配する will have to be bent if, say, I someday decided to 与える／捧げる to the American 医療の 協会 (simple code would be amme... same as アマゾン 医療の... not 許すd because this is the （米）棚上げする／（英）提議する's 最初の／主要な 重要な, each must be different. A different code would be 要求するd for the American 医療の 協会. I'd probably use ama in this 事例／患者.)
Next, just to get things started, we'll create a 天然のまま form for entering some 見本 data. Use the wizard....
... and then enter the 見本 data, so we have something to "chew" on. You can put "taxFrntNurs" or something 類似の in the ChariTaxName field. It is there because I really am going to use this database, but you don't need to fuss with looking up, using the real 公式の／役人 指名するs of the charities.
Life is short. The "権利" way to do this will probably take five times as long to learn as all the time you would spend doing it the "wrong" way. I will try to 拡大する this 事例／患者 熟考する／考慮する in 予定 course with explanations of how to do it the 権利 way... but for now, here are some ideas for quick and dirty 解答s....
We'll do a 報告（する）／憶測 for 2006.
Start designing a new query, using the design 見解（をとる）.
追加する the "Gifts" （米）棚上げする／（英）提議する to the design window from the "追加する （米）棚上げする／（英）提議する or Query" dialog box.
In the grid at the 底（に届く） of the design window, 始める，決める things up as follows. (You may have to 二塁打 click on ChariTaxName to "wake the system up". Once you've got that in as the field for the first column, you can use the listbox to 得る the 指名するs of the other fields.
Field: ChariTaxName G2005 偽名，通称: Charity 寄付 （米）棚上げする／（英）提議する: Gifts Gifts Sort: 上がるing 明白な: y y 機能（する）／行事: Criterion: IS NOT EMPTY
Wow! In 準備するing that for you, I 遭遇（する）d something weird even for a computer!
To put that IS NOT EMPTY criterion in, this is what you do....
Type EMPTY in the 独房. Backspace to the start of the 独房, and type, without spaces, ISNOT. Use backspace again, go 支援する to where you must, and put the two spaces in. NOW you can run the query, and you will get a sensible result! (Putting the "IS NOT EMPTY" criterion in stops the query from 含むing Techoserve, which didn't receive a 寄付 in 2005. Why didn't I use the more easily entered ">0"?
a) I'm stubborn. Not very clever, but stubborn. (It's how I've learned a few things about the wretched machines.)
b) If nothing has been entered in a field, can you be sure that "nothing" will be 裁判官d to be more than 無? Probably... but I'd rather rely on the sure-to-work (if there's no bug) "IS NOT EMPTY".
A word about the "偽名，通称" 列／漕ぐ／騒動. What you filled in there gets used for the query's column headers, and you will 言及する to those fields by those 指名するs if you, say, use a 報告（する）／憶測 to 陳列する，発揮する the results of the query.
Save the query as TaxReport2005. It would probably "do" for a quick and dirty 名簿（に載せる）／表（にあげる） of your gifts for the year, but it is very little work to go a step さらに先に.
Now switch to the 報告（する）／憶測s section of ooBase. Invoke "Use Wizard to Create 報告（する）／憶測"
Hmmm. Have I given you bad advice? We have a query called "TaxReport2005", and a 報告（する）／憶測 called "TaxReport2005". Only one is truly a 報告（する）／憶測, but they are both part of 生成するing the 報告（する）／憶測 you need for とじ込み／提出するing your 税金s. Maybe it would have been better to call the query "QueryForTaxReport2005", but as the とじ込み／提出する 拡張s and 陳列する，発揮する filtering already keep the queries and the code-for-生成するing 報告（する）／憶測s separate, I 嫌疑者，容疑者／疑う we can all live with my "bad" 指名するs.
Run the 報告（する）／憶測. It should work pretty 井戸／弁護士席 straight out of the designer.
Things you can do to make it fancier:
の近くに the 報告（する）／憶測, if you have it open. (Re-)open in design 見解（をとる）. (権利 click on the 報告（する）／憶測 指名する in the ooBase main 事業／計画（する） 管理／経営 window, select "Edit")
In the edit 見解（をとる）, you can....
Look at the 肩書を与える 妨げる／法廷，弁護士業. You are working on a clever ooWriter 文書. Don't imagine you can be too clever about what appears in the （米）棚上げする／（英）提議する where your data will appear. (It has some Latin gibberish standing in for your data for the moment.) But you can "do things" to how even that appears. And you can change the headers on the 文書, move the （米）棚上げする／（英）提議する to where you want it, etc, etc, just as if you were (because you are) working in the wordprocessor part of Open Office.
Look Out: Two bits of Bad News, one small, one big... maybe
Little Bad News: I couldn't find a way to run the 報告（する）／憶測 when I was though editing, apart from saving my edits, の近くにing the edit window, invoking the 報告（する）／憶測. Many other things, e.g. the query designer, have buttons which let you run the query straight from the designer. By the way: I wouldn't "cheat", and run a query or 報告（する）／憶測 from the ooBase main 事業／計画（する） 管理／経営 window without first の近くにing any open designer windows. I've got into frozen machines that way.
Big Bad News: Want to have a total at the 底（に届く） of the page, telling you the total of the 寄付s? I don't think you can get this with the ooBase 報告（する）／憶測 Wizard. But! You can get it, with just a little 成果／努力 that will be rewarded again and again if you 昇格 your ooBase to 2.4 (if necessary) and use the excellent, fully 統合するing, 報告（する）／憶測 建設業者 from Sun Microsystems. I've done a tutorial with 取り付け・設備 指示／教授／教育 and an introduction.
Once you've 任命する／導入するd ooBase 2.4 and 追加するd the 報告（する）／憶測 建設業者 拡張, then on the ooBase main 事業／計画（する） 管理／経営 window, when you have selected "報告（する）／憶測s", you will have a "Create 報告（する）／憶測 in Design 見解（をとる）" 選択 in the 仕事s pane. 二塁打 click that, and the 報告（する）／憶測 建設業者 opens.
Open the 報告（する）／憶測 航海士, click on the 最高の，を越す item, "報告（する）／憶測", and in the Data tab of the 報告（する）／憶測's 所有物／資産／財産s, 明示する Content Type: （米）棚上げする／（英）提議する, Content: Gifts. A 名簿（に載せる）／表（にあげる） of 利用できる fields will open up. You may think there is a glitch in the 報告（する）／憶測 Designer... When you've selected "Gifts", you may not, at first, see the 約束d 名簿（に載せる）／表（にあげる） of the fields of "Gifts" in the 追加する Field dialog. 恐れる not. All you have to do is leave the Content listbox, and the field 指名するs appear.
Drag ChariTaxName and G2005 to the "詳細（に述べる）" 禁止（する）d of the 報告（する）／憶測 design. Resize, 改名する and relocate the fields that result, and make the 詳細（に述べる） 禁止（する）d no higher than it needs to be to 融通する the two data fields on a 選び出す／独身 line. Move the label fields (the ones with the text in them) to the Page Header 禁止（する）d.
My 報告（する）／憶測 （機の）カム out in alphabetical order, without any special 成果／努力 on my part. This puzzled me at first, but I'm pretty sure the 記録，記録的な／記録するs were 現在のd in that order because, in the absence of any other sorting 命令（する）, the 記録，記録的な／記録するs appear as if sorted on the 最初の／主要な 重要な, ChariID. As an 実験, I entered a new 記録，記録的な／記録する with ChariID='fff' and ChariTaxName="Zebedee". Lo and behold, the charities were 名簿（に載せる）／表（にあげる）d ALMOST in alphabetical order, an artifact of the similarities between their ChariIDs and ChariTaxNames... BUT: Zebedee appeared just after アマゾン 医療の (ChariID=amme) and before Frontier Nursing (ChariID=Frnu). If you want to be sure of the order, or 明示する that the 報告（する）／憶測 be printed によれば the values in MySortOrder, you use Sorting and 配合, or you base the 報告（する）／憶測 on a query, which has had sorting built into it.
Click on the button to call up the Sorting and 配合 dialog box. 追加する the 関連した field 指名する to the 名簿（に載せる）／表（にあげる）. (To get rid of one, 権利 click on the gray box to the left of the field 指名する, select 削除する.)
A new 禁止（する）d will appear on the 報告（する）／憶測. Drag its 底（に届く） 辛勝する／優位 up, until the 禁止（する）d has no width. (Or use the 所有物／資産／財産s dialog to 明示する that the header not be 現在の.) Run the 報告（する）／憶測, it will be ordered によれば the field you 明示するd.
自白. While this 報告（する）／憶測 is better for all sorts of 推論する／理由s, not least 申し込む／申し出ing value totals (we'll get to that in a moment), Technoserve is 名簿（に載せる）／表（にあげる）d, even though we 寄付するd nothing to it in 2005. Ah! Had we based the 報告（する）／憶測 on the same query as we used before, the Technoserve line would not have appeared. (And there is another way to solve the problem, even with the 報告（する）／憶測 based on the （米）棚上げする／（英）提議する. Go into the Data tab of the 報告（する）／憶測's 所有物／資産／財産s, and you can 明示する a filter. This time instead of "IS NOT EMPTY", you 始める，決める the filter to ("G2005" IS NOT NULL). Bah! But it does 達成する the 願望（する）d 影響, and the form can even be given 報告（する）／憶測 headers and 寄付 total 報告（する）／憶測s, the same way as we will do in the query based form, in a moment. (This little 発見 about four hours into putting this tutorial together! It even 生き残るs the いつかs-total-難破させるing absence of a value in G2005 for Technoserve!))
=====
The above 構成要素 took about an hour to 生成する... all was going やめる 井戸／弁護士席... and then I 攻撃する，衝突する a major 障害. I must have spent several hours to get to the 底（に届く） of a few things that you are going to learn how to navigate with just a little reading. My stubbornness at work again.
It is really 平易な to 生成する a 報告（する）／憶測 with a total showing how much was given to the charities. It is also very 平易な to 始める，決める something up that "should" work... and doesn't.
This time we're going to 始める，決める up a 報告（する）／憶測 based on the query. Do the に引き続いて...
Once again start a 報告（する）／憶測, and put the Charity and 寄付 data fields in the 詳細（に述べる） 禁止（する）d, with their labels in the Page header 禁止（する）d. Do not bring up the Sorting and 配合 dialog again. The query already 明示するs a sort order. If you have a sort 禁止（する）d, it seems to 完全に flummox the totaling 機械装置.
Before we を取り引きする putting the total of 寄付s on the page, we have to open up some new 禁止（する）d.
権利 click somewhere in the design window, inside the area covered by the 支配者s, but not over any of the things you've placed in the 報告（する）／憶測 so far. The menu you get should 含む "挿入する 報告（する）／憶測 Header/Footer". Click on that. You should now have the に引き続いて 禁止（する）d....
始める，決める the 報告（する）／憶測 Header 禁止（する）d's "明白な" 所有物／資産／財産 to No.
Use the 追加する Field dialog box to 追加する again the 寄付 field. Put this instance of the 寄付 field in the 報告（する）／憶測 Footer 禁止（する）d. This probably seems an 半端物 thing to do, but it will be the way we create our "total of 寄付s" 生産（高）.
When you've 追加するd the field, you'll again see a label and a data field. Change the text in the label to "Total 寄付s" (You'll have to do a bit of clicking first, to get just the label selected.)
Then click on the data field. Change the 入ること／参加（者）s on the Data 所有物／資産／財産s tab to....
Data Field Type: 機能（する）／行事 Data Field: 寄付 機能（する）／行事: Accumulation 範囲: 報告（する）／憶測
Save (I called it "ReportBuilderTax2005") and run the 報告（する）／憶測!
======
I must 収容する／認める a 確かな exhaustion at this point. It really shouldn't be so difficult... but databases are more difficult than other 使用／適用s you may have used.
If you've had enough, stop reading here. The に引き続いて 瀬戸際s on "rambling"... but if you are keen, you may glean some things that you may find 利益／興味ing! I'm going to 調査する two little mysteries, annoyances, what-chu-ma-call-its....
If you try to 生成する a "total 寄付s" 人物／姿／数字 from a 名簿（に載せる）／表（にあげる） of 記録，記録的な／記録するs in which one has no value in the 寄付 field, your total will only 含む the 人物／姿／数字s に引き続いて the 記録，記録的な／記録する with an empty 寄付 field. I suppose this is almost reasonable... the poor computer is 追加するing (蓄積するing) values into a running total as it 生成するs the 報告（する）／憶測. Perhaps you or I would just skip over an empty field, but the computer, poor literally minded beast that it is, tries to 追加する a null field, and gets 混乱させるd.
The other thing that I spent time on, without solving (yet) was the 事柄 of having text in the 報告（する）／憶測 header. It would be nice... and not too much to ask?... if the first page of a 報告（する）／憶測 looked like....
My Nice 報告（する）／憶測 for 2005
Charity / 寄付
Americares 100
アマゾン 医療の 100... etc, etc....
... and then, in my perfect world, page 2 would look like....
Charity / 寄付 IRC 100 Mayo Clinic 500... etc, etc....
In other words, we want "My Nice 報告（する）／憶測 for 2005" once at the 最高の，を越す of the first page, and "Charity / 寄付" on every page, underneath the 報告（する）／憶測 header on the first page.
井戸／弁護士席.... I tried lots of things.
If you make the 報告（する）／憶測 Header just "My Nice 報告（する）／憶測 for 2005", and the Page Header "Charity / 寄付", then the first page comes out as....
Charity / 寄付 My Nice 報告（する）／憶測 for 2005 Americares 100 アマゾン 医療の 100... etc, etc....
Yep, you got it... Page Header goes above 報告（する）／憶測 Header.
I thought I was 存在 clever when I tried making the 報告（する）／憶測 Header all of the に引き続いて....
My Nice 報告（する）／憶測 for 2005
Charity / 寄付
... and the Page Header "Charity / 寄付", and then I tried to 抑える the Page Header for the first page. 設立する two ways....
There's a 条件付きの Print 所有物／資産／財産 for the Page Header, and I'm sure that something like "(Print) IF PageNumber>1" that would do what I want... but I couldn't find the 魔法 incantation.
There's also a 所有物／資産／財産 of the 報告（する）／憶測 that lets you 明示する that the Page Header should not appear with the 報告（する）／憶測 header, AND the 報告（する）／憶測 Header has a "軍隊 New Page" 所有物／資産／財産 which can be 始める，決める to "非，不，無"... but I couldn't get any 記録，記録的な／記録するs printed on the first page, just the 報告（する）／憶測 Header, if I said I didn't want the Page Header appearing with the 報告（する）／憶測 Header.
Ah 井戸／弁護士席... these little mysteries certainly keep time from hanging 激しい on my 手渡すs, anyway. I hope the SOLVED mysteries were useful to you.
================
I do realize that by just stopping here, I have left a number of questions unanswered, 面s of the charity giving database 事例／患者 熟考する／考慮する not 調査するd. I will try to come 支援する to this and 延長する it. In the 合間 I hope you'll see the cup as half 十分な.
I stopped because I 手配中の，お尋ね者 to get what's above online for you. 生成するing the essay is one thing. Even though it was written with its 未来 use in mind, going from the essay to a published web page was about another hour's work.
I dislike 'fancy' websites with more 関心 for a flashy 外見 than for good content. For a pretty picture, I can go to an art gallery. Of course, an attractive 場所／位置 WITH content deserves 賞賛する... as long as that pretty 直面する doesn't cost download time. In any 事例／患者....
I am trying to 現在の this 構成要素 in a 判型 which makes it 平易な for you to USE it. There are two 面s to that: The way it is 分裂（する） up, and the way it is 地位，任命するd. See the main 索引 to this 構成要素 for more （警察などへの）密告，告訴（状） about the way it is 分裂（する） up, and the way it is 地位，任命するd.
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.
If you would like to use 構成要素 from this 場所／位置, say on a CD, my page about permitted use may save you some time. As my pages do get updated from time to time, it would seem to me that you would serve your readers better by giving them links to my pages rather than copying them as they are at a point in time. But I realize that internet 接近 制限s may make copying a page necessary.
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 . . . . .