Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org|
このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。 |
You may find that the database 存在 shipped with OpenOffice (ver.2 and higher) delights you as much as it has me. This page tries to help you use it.
Forget anything you may have heard about Adabas, which （機の）カム with 星／主役にする Office, the 商業の 見解／翻訳／版 of Open Office 1. The 現在の Open Office's database, "Base", aka "ooBase", is 関係のない. And remember that Open Office, 含むing ooBase, is 解放する／自由な! But don't let that fool you. And it's not new. Big organizations, 政府 and 非軍事の, are 可決する・採択するing it as their 基準 office 控訴... and saving million$, but still Getting The 職業 Done.
There's more about ooBase in the main 索引 to this 構成要素.
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 more fully explained, and there's another tip, at my 力／強力にする Browsing page.)
Page contents © TK Boyd, Sheepdog ソフトウェア, 3/06-10/17.
Part of the art of creating good databases lies in choosing what fields will appear in what （米）棚上げする／（英）提議するs. The （米）棚上げする／（英）提議するs are the bedrock of any database. There are serious 支配するs about what should and should not be in them... try to find discussions of data 正常化 to help you start learning about those 支配するs.
The 支配するs support a couple of ideas:
In 関係 with that last point, consider the に引き続いて database 使用／適用, and try to imagine the many, many 類似の 状況／情勢s.
Imagine that you are keeping 跡をつける of some 株式市場 投資s. (Yes, I know that what follows would not serve an 投資家's real needs. It is just to illustrate a point.)
In the database we are going to have a 記録，記録的な／記録する for each 持つ／拘留するing. If Fred had...
....then he'd have 3 記録，記録的な／記録するs in his database. Each 記録，記録的な／記録する would have the に引き続いて fields: Company 指名する, Number of 株 owned, Value of a 選び出す／独身 株. (That last field would be a 苦痛... if Fred 手配中の，お尋ね者 an up-to-date idea of his 株' total value, he'd have to go into the database and change the values in each of the "PerShare" fields.)
You might think it would be nice to have a "Value of the 持つ／拘留するing" field. I.e., if IBM were 価値（がある） $80 per 株, Fred's 100 株 would be 価値（がある） $8000, and that "8000" could be 蓄える／店d in the （米）棚上げする／（英）提議する. This would be a Bad Idea: In a sense you would breaking the "Don't enter something twice" 支配する (the "Value of 持つ／拘留するing" field would, essentially, duplicate a combination of the "株" and "PerShare" fields), and it would break the "Don't enter things you don't need to" 支配する.
But that doesn't mean that Fred can't make the computer work out for him that the IBM holdings are 価値（がある） $8000! How he gets that （警察などへの）密告，告訴（状）, the 権利 way, is the 支配する of this tutorial!
Before we proceed: A 詳細（に述べる）. 投資家s will want to know the value of their 株 on 明確な／細部 dates. The per 株 value of a 株 変化させるs from day to day. The database, as 述べるd here, will either need all the prices re-entered for whatever day is of 利益／興味, or a more コンビナート／複合体 database ("easily" created) will be needed. To keep things simple, which is all we need for the 技術s under consideration, just think of this database of a way to know the cost of different 投資s, and imagine that the PerShare 人物／姿／数字 記録，記録的な／記録するs what was paid for the 株 on the day they were 購入（する）d. (And yes, I do realize that if this database were to be used in the real world, the date the 株 were 購入（する）d would also be in the （米）棚上げする／（英）提議する.)
And a bit of bad news before we proceed: As 述べるd in the main part of this tutorial, you can have a form to 見解（をとる） （警察などへの）密告，告訴（状） from a database, 完全にする with some calculated fields (i.e. the "Value of 持つ／拘留するing" （警察などへの）密告，告訴（状）). However, you will have, for now, to use a separate form if you want to make changes to any （米）棚上げする／（英）提議する or （米）棚上げする／（英）提議するs underlying the form with calculated fields. And, more bad news, you will probably have to click buttons to make the "info 陳列する，発揮する" form update itself after any changes on the "data 入ること／参加（者）" form. Sorry! I'm learning all the time, and may "割れ目" this one いつか... but for now, here's "a way", be it ever so 天然のまま...
Some earlier tutorials give you more support than this one does. If you find it difficult to 完全にする the 仕事s 明示するd below, you might want to work though some of the earlier tutorials first.
Create a （米）棚上げする／（英）提議する called "Main". Do it however you wish, with the wizard, or in design 方式. Be sure to 始める，決める the first field as the 最初の／主要な 重要な, with the "Autovalue" 所有物／資産／財産 始める，決める to "Yes".
Define the fields with the に引き続いて field types, 指名するs, lengths, etc, as shown:
ID (最初の／主要な 重要な, Integer, AutoValue)
株 (Integer)
PerShare (Number, length 16, decimal places: 2)(This for price)
Company (Text [varchar], length:5)
Put some data in the （米）棚上げする／（英）提議する. Two 記録，記録的な／記録するs will 十分である.
の近くに the （米）棚上げする／（英）提議する.
Now that you have the （米）棚上げする／（英）提議する, there are two ways you can 供給する yourself with a way to edit what is in it. For simple things, you may need nothing more than a simple form. But if you want a calculated field 陳列する，発揮するd, then this morning (July 2009, and again March 2010) I can only do that with a form based on a query. (I could have sworn I had a form working with a calculated field, without a query in 2009... but I can't do it now.) The calculated field will show the value of the 株.
Create a query. I used the wizard.
含む ALL of the fields. (You may not need to, but for now: 含む them, just in 事例／患者.)
Do not 始める，決める a sort order. (You probably could, but I'm trying to keep this simple.)
Do not 始める，決める any search 条件s.
Step 4: 受託する the default "詳細（に述べる）d" type query. This will 許す you to skip a few steps.
Next step: In at least some pre-見解／翻訳／版 3.1 variants of ooBase, at the next step, the default 偽名，通称s 含む "Main." in 前線 of "ID", "株", etc. If you are using an old 見解／翻訳／版, and seeing this, edit the "Main." off of the 偽名，通称s. (E.g., make the 偽名，通称 for "Main.株" just "株", etc.). If you are using ooBase 見解／翻訳／版 3.1, you won't need to do this, and the step where you will be able to see the 偽名，通称s will be step 7. I 嫌疑者，容疑者／疑う it was step 7 for a long time... but there was what I think was a typo in this tutorial, and the tutorial said the "偽名，通称s" step was step 5. (If you can 確認する that it was once step 5, I'd be 利益／興味d. Or if you are still using ooBase 2.4, please check what it's "偽名，通称s" step is for me? (And then 昇格 yourself!)
Call the query "QueryWithCalc"... even though it doesn't have a calculated field yet!
Before you click "Finish" to leave step 8, select "修正する query" for what happens next.
The main design window for the query should open. Across the 底（に届く） is a （米）棚上げする／（英）提議する, with four 居住させるd columns. Click in the "Field" 独房, the 最高の，を越す one, of the fifth column, the first empty one. Enter....
株*PerShare
... 存在 careful to use the same capitalization as you used in 指名するing those fields... it does 事柄. Do not be alarmed if ooBase puts some quotation 示すs around the 指名するs. If you have a field 指名する with spaces in the 指名する, enclose the 指名する in 引用する 示すs, e.g.
"Per 株"
Next, fill in Value of 株 for the 偽名，通称 of the fourth column. (It doesn't have to be bold, I just 手配中の，お尋ね者 to 避ける using 引用する 示すs to delimit the 偽名，通称, as you shouldn't use them with your 入ること／参加（者）.)
Put a tick in the "明白な" box, if it isn't ticked already.
Finally, save the query 鮮明度／定義 and run it. You should see sensible results, and you can alter the contents of the database.... if all is 井戸／弁護士席. (Don't fool with the "ID" field's contents.) (The time I tried making a query without the ID field, I could see sensible results... but not change anything.)
I hope you wouldn't 推定する／予想する to be able to 直接／まっすぐに change the "Value of 持つ／拘留するing" 入ること／参加（者）? Think about it. You can try.. no 害（を与える） will come of doing so.
N.B. If you find that you can change the number of 株 in a 記録，記録的な／記録する, or change the cost per 株 field, then when you do it, the "持つ／拘留するing value" will not change すぐに. It will change when you...
So! We have a query that fetches the number of 株, and the value per 株 from the （米）棚上げする／（英）提議する, and then 作品 out for us the value of the 持つ／拘留するing. In a sense, we have 達成するd our goal... but it would be better to 圧力（をかける） on, and 完全にする 付加 steps....
Now use the wizard to create a new form.
In step 1, select our newly created query "QueryWithCalc", and ask for all of its fields to be 含むd in the form.
Step 2: Don't 始める，決める up a sub-form, just click "Next".
Step 5: I used a "Data Sheet" 協定; I don't 疑問 others would work, too.
In step 6, 始める，決める data 入ること／参加（者） to "陳列する，発揮する all", without "change" 制限s.
Step 7: Any style will do.
Step 8: Use "FormWithCalc" for the form's 指名する, or "FormBasedOnQueryWithCalc", and tell the wizard that you want to work with the form after it is created.
Click "Finish", to 完全にする the wizard, and you should find you have a good interface to the （米）棚上げする／（英）提議する, with the calculated field telling you the value of each 持つ／拘留するing.
Ta da? Yes... if you are only trying to 検査／視察する data in the （米）棚上げする／（英）提議する, and learn the values of different holdings, i.e. the answer to "number of 株 multiplied by value per 株."
At this point, this morning (9Mar10, ooBase 3.1.0, WinXP) I am able to change data in the underlying （米）棚上げする／（英）提議する 経由で the query based form! As long as, for now, I only change data in 存在するing 記録，記録的な／記録するs.... but see below.
I have 格闘するd with this sort of thing again and again, getting different answers every time! I have not (yet!) 実験（する）d altering data in （米）棚上げする／（英）提議するs from forms 陳列する，発揮するing the results of a query pulling data from more than one （米）棚上げする／（英）提議する. That may be A Different Story.)
If at this point you try to 追加する a new 記録，記録的な／記録する, i.e. a new 列／漕ぐ／騒動 of data, you will probably get "Error 令状ing data to database... Input 要求するd... 'Value of 株'...". But! We can 直す／買収する，八百長をする this! There are two ways. In either 事例／患者, start by の近くにing the form.
This is a little more "cumbersome" that the second, but it 控訴，上告s to my belief that the more checking you have the better. The second 解答 turns off more than you need to.
Open the form for editing. 権利 click on the column 長，率いるing "Value of 株" (the calculated field).
Click on the "Column..." 選択. A dialog 長，率いるd "所有物／資産／財産s: Formatted Field" should open. Select the "Data" tab. 始める，決める "Input 要求するd" to "No".
That should do it! Next I'll give you an 代案／選択肢 解答 in 事例／患者 for some 推論する／理由 you don't like that. (Or in 事例／患者 it won't work for you. If it won't, and you are using ooBase 3.1.0 or later, please 接触する me, 特記する／引用するing "fdb1calcf1", and I will look at this again.)
The form should be の近くにd. In the ooBase main 事業／計画（する） 経営者／支配人 window, select "Forms" in the left 手渡す パネル盤, a then 権利 click on "FormWCalc". Click on the "Database" 入ること／参加（者） at the 底（に届く） of the pop up menu. Click on "前進するd Settings". 除去する the tick in 前線 of "Form data input checks for 要求するd fields".
Save the edited form. Open it for normal use... you should now be able to enter data in the （米）棚上げする／（英）提議する through the form which is based on the query. If you can't, and you are using ooBase 3.1.0 or later, please 接触する me, 特記する／引用するing "fdb1calcf1", and I will look at this again.)
If you worry (as I think you should) about the ramifications of this turning off of checks, I can at least 安心させる you that some checks remain in place. For instance, I tried to enter "xx" into a field that was of type "integer". The "xx" was 変えるd to a 無.
There is a "天然のまま" answer you can use when you can't get data to pass 支援する to your （米）棚上げする／（英）提議するs from a form: use 多重の forms.... one (query based) with whatever you need to see, and another, simpler, form (or forms) for changing data in the （米）棚上げする／（英）提議する(s).
Don't 落ちる to the 誘惑 of working 直接／まっすぐに with a query in hopes of changing what is in a （米）棚上げする／（英）提議する. When you change 入ること／参加（者）s in the result of a query, it will appear to work, but you are only changing what you see on the 審査する, not what is in the underlying （米）棚上げする／（英）提議する.
I hope you have a sensible result, after working through what is above. 陳謝s if the answer is still 欠陥d at this time... I've spent hours on this over the years. But do "complain" if need be!
Ha! 進歩? 予選 実験s 示唆する that the above techniques won't work if your query draws data from more than one underlying （米）棚上げする／（英）提議する. Sigh. But a least a 候補者 for why the thing "作品" いつかs, and not others. So how DO we do it in multi-（米）棚上げする／（英）提議する 状況／情勢s?
An enquiry at the excellent oooFurum.org gave rise to this （警察などへの）密告，告訴（状） from Villeroy, who has 供給（する）d many excellent answers for the community over the years. 公式文書，認める that he supports my idea that you need to 含む the 最初の／主要な 重要な in the form or query, even if you don't 陳列する，発揮する it. But 公式文書，認める the 付加 point he makes: You DO need to 陳列する，発揮する the 最初の／主要な 重要な if its "autovalue" 所有物／資産／財産 isn't 始める，決める to "yes". Also, 式のs, 公式文書，認める that he says you can't use the techniques above on a query 製図／抽選 （警察などへの）密告，告訴（状） from more than one （米）棚上げする／（英）提議する.... unless, as they say, you know さもなければ??
Your form is writable if it is bound to some 記録，記録的な／記録する 始める，決める from a 選び出す／独身 （米）棚上げする／（英）提議する and if the （米）棚上げする／（英）提議する's 最初の／主要な 重要な is 含むd. This means that the form is bound to the entire （米）棚上げする／（英）提議する and the （米）棚上げする／（英）提議する is editable OR the form is bound to some 列／漕ぐ／騒動 始める，決める like SELECTFROM "SIngle_Table" WHERE ... ORDER BY... This 列／漕ぐ／騒動 始める，決める is editable just like the （米）棚上げする／（英）提議する if and only if the field 名簿（に載せる）／表（にあげる） 含むs the 最初の／主要な 重要な of the 選び出す／独身 （米）棚上げする／（英）提議する. If the PK is an 自動車-value you don't have to 陳列する，発揮する the PK by means of a form 支配（する）／統制する. 明白な or not, It is part of the form's 列／漕ぐ／騒動 始める，決める. Subforms follow the same 支配するs. A pair of subform and parent form 反映するs a one-to-many relation and makes this relation editable. The editable parent selects editable 記録，記録的な／記録するs in the subform.
As I said above, I've 格闘するd with this for some time. The に引き続いて may be useful of 利益／興味ing if you find that what's above doesn't Just Work.
In a discussion at the Open Office 会議, two comments were made, which may be of 利益／興味:
The first 示唆するs that what as of 9Mar10 I think 作品 never has. But I've been through periods of not 存在 able to make it work!
The second 示唆するs up an 利益／興味ing 補欠／交替の／交替する path to a 解答. I believe that answer is even ふさわしい to forms that 陳列する，発揮する more than one 記録，記録的な／記録する at a time. I wonder if it would 要求する a 十分な blown query, or whether the sub-form could be asked more 直接／まっすぐに just to 陳列する，発揮する the result of "株"*"PerShare". (I didn't have much luck when I tried to do this without a query... but I live in hope that it CAN be done, at least for a form 陳列する，発揮するing just one 記録，記録的な／記録する. (There are ways if you want to get into using 大型のs.)(追加するing a sub-form IS covered in another of my pages, but that page 会談 about a 広大な／多数の／重要な 取引，協定 else! (追加するing the subform isn't hard... when you know how... but what you need to do ーするために 追加する a subform may not seem "obvious"... it wasn't to me, anyway!))
(Another discussion which may be useful if you don't mind using 大型のs: oooforum thread.)
Another oooforum.org discussion which may be useful is a form that can BOTH be used to enter new data, AND which can 陳列する，発揮する a calculated result from fields. Also uses a 大型の.
Hmmm... "stranger, stranger and harder...."
In 調査するing a question from a reader, 3 March 10, I've つまずくd into something that may or may not be true, may or may not be useful....
My 現在の best guess... needs work... is....
If you just want to look at some data, e.g. the 投資 data used as the example at the 最高の，を越す of the page, AND have a calculated field, then The Way To Go is to 始める，決める up a query to "収穫" the data, and calculate what will be in the calculated field... as 始める，決める out in the main part of what starts at the 最高の，を越す of this page.
** B U T **: If you want to ADD OR EDIT RECORDS 経由で the same form, then things get a little tiresome. However, it MAY (P.S. I now (9 March 2010) think that the に引き続いて is unnecessarily 複雑にするd, that the simple answer in the main part of this page WORKS.) be possible to proceed as follows. What follows is NOT extensively 実験（する）d, and the text needs work, but may get you where you want to go, if you want to be a 開拓する!
始める，決める up a form. Put a datagrid on it, based 直接／まっすぐに on the underlying （米）棚上げする／（英）提議する. Continuing with the example I started with, on that you would DISPLAY the three "obvious" fields: 株, PerShare, Company. I think you'd want the ID field 利用できる... it may be anyway.... but not showing.
始める，決める up a query to return ID and "株 * PerShare"
追加する a subform to the main form, have it 陳列する，発揮する the "株*PerShare" part of the query.
I THINK you can get that subform lined up on the 審査する with the main form, creating something that almost looks like one datagrid with 4 columns. The human won't know (or care) that the first 3 come from one 支配（する）／統制する, and the last from a separate 支配（する）／統制する... but that MAY get you around the problem of creating a form which can 陳列する，発揮する calculated fields AND be used to edit the underlying （米）棚上げする／（英）提議する. (If any reader KNOWS this idea is a 非，不，無-starter, or better yet, tries it and gets it to WORK!!, I'd be delighted to hear from said reader!)
============================It makes little sense to show the 記録，記録的な／記録する ID on the form 陳列する，発揮するing the （米）棚上げする／（英）提議する's data and the calculated values of the 株 holdings. It, in this example, is just an "内部の" thing, of 利益／興味 only to ooBase. I think that the ID field must remain in the query if you have a query based on more than one （米）棚上げする／（英）提議する (which may or may not be able to pass data 支援する to the underlying （米）棚上げする／（英）提議するs, but you are 許すd to do the に引き続いて. (At the time of 令状ing, I 港／避難所't 実験（する）d these techniques with queries pulling data from 多重の （米）棚上げする／（英）提議するs. 陳謝s if since 令状ing this, I've gone on to the more 前進するd 事例／患者, 設立する it working, and forgotten to 除去する this 警告.)
Open the form (the one based on the query) for editing.
権利-click on the "ID" column 長，率いるing. Click on "Hide columns". Save your form.
The form should still work, but not 陳列する，発揮する the ID column, which is a necessary column, for the computer, but one of little 利益／興味 to a 使用者 of the database.
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.
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 . . . . .