Open Office Database Tutorials
Using the Design 見解（をとる） to create a database's first （米）棚上げする／（英）提議するs

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 ソフトウェア ®, 2/06-5/09.

A nice, simple, short 公式文書，認める... hardly a tutorial at all! ________

In the first tutorial in this series, I 示唆する that you use the wizard to create your first （米）棚上げする／（英）提議する. Perhaps that is best for a beginner.... but it really isn't necessary most of the time. (More on when it is necessary in a moment. In some other tutorials, the suggestion to use the wizard is a hangover from my 早期に, ignorant, days.)

First I need to be sure you are （疑いを）晴らす about something. I have not made it 完全に （疑いを）晴らす 以前. And of course, you may not have read some of my earlier tutorials. In any 事例／患者, the point 耐えるs repeating. The point 適用するs to all flavors of SQL. ooBase is, essentially, a 前線 end giving you 接近 to many database engines. I hope you are using it to 接近 the HSQL engine which comes with Open Office... that leaves several より小数の things to "go wrong". If so, you are working in a SQL 環境.

When working with SQL, when you speak of "a database", you are いつかs referring to something akin to a コンテナ. A SQL "database" 含む／封じ込めるs one or more （米）棚上げする／（英）提議するs, 加える 無 or more forms, queries and 報告（する）／憶測s. (The 称する，呼ぶ／期間／用語 gets used in other ways, too, but the "コンテナ" meaning is an important one.) That コンテナ does a number of things, one of which is to "持つ／拘留する" all of the bits of the database in a 選び出す／独身 とじ込み／提出する. You don't get a separate とじ込み／提出する for each （米）棚上げする／（英）提議する, form, query, 報告（する）／憶測.

When working with SQL, you first create the database, i.e. the "コンテナ". 最初, it doesn't 含む／封じ込める even a （米）棚上げする／（英）提議する. (It is pretty useless like this... it is just the コンテナ, which is ready to acquire a （米）棚上げする／（英）提議する, and thus the beginnings of its usefulness.)

Creating the database with ooBase is 平易な, and is explicitly explained, in 詳細（に述べる）, in all of my introductory tutorials.

The second step of the ooBase "new database" wizard asks you to select either "Open the database for editing" or "Create （米）棚上げする／（英）提議するs using the （米）棚上げする／（英）提議する wizard" as what you do after the wizard 完全にするs. I was 混乱させるd by this terminology. It isn't wrong, but it 誤って導く me.

When you run the New Database Wizard, the database gets opened 関わりなく which 選択 you choose. If you choose the first, you are not electing to edit data that you have 蓄える／店d in some （米）棚上げする／（英）提議する... there are no （米）棚上げする／（英）提議するs yet.

If you just "open the database", you will find yourself looking at the main ooBase 事業／計画（する） 管理／経営 window, but there will not yet be any （米）棚上げする／（英）提議するs, forms, queries or 報告（する）／憶測s. Your first 仕事 will be to create at least one （米）棚上げする／（英）提議する.

If you elect to "create （米）棚上げする／（英）提議する....", you will also open the database. You can't work on any part of it unless it is open. And until it has a （米）棚上げする／（英）提議する, there's nothing to work on. The "create （米）棚上げする／（英）提議する...." 選択 really せねばならない be called "Open database and go straight into creating a （米）棚上げする／（英）提議する, using the wizard."

Good news! Things start getting easier now!

A moment ago, I said "Your first 仕事 will be to create at least one （米）棚上げする／（英）提議する." There are always two ways to create a （米）棚上げする／（英）提議する...

• "Create （米）棚上げする／（英）提議する in Design 見解（をとる）" (i.e. using the Design 見解（をとる） 道具), or
• "Use Wizard to Create （米）棚上げする／（英）提議する."

There is no difference between the resulting （米）棚上げする／（英）提議するs.

どこかよそで, I often 示唆する that you invoke the "... using （米）棚上げする／（英）提議する wizard" 選択. The more I use ooBase, the more I prefer the 代案／選択肢.... create the database, and then use "Open database for editing" at the end of creating the database (the "コンテナ"). If you do this, you are taken to the ooBase 事業／計画（する） 管理／経営 window, the one with three panes: "Database", "仕事s", and a third pane which is "（米）棚上げする／（英）提議するs", "Queries" "Forms" or "報告（する）／憶測s", depending on what you have selected in the "Database" pane. It looks the way things look when you re-open a database you've done some work with. Except, this first time, there are no （米）棚上げする／（英）提議するs, forms, queries or 報告（する）／憶測s yet. Click on "（米）棚上げする／（英）提議するs" and then "Create new （米）棚上げする／（英）提議する in design 見解（をとる）".

Using the design 見解（をとる） to create a （米）棚上げする／（英）提議する

There's not much to tell you. Invoke that 選択, and you will be 現在のd with a datasheet 陳列する，発揮する, i.e. a 陳列する，発揮する that looks very like a spreadsheet. There are 多重の 列／漕ぐ／騒動s, three columns. At the 底（に届く） of the page there's an area where you can (結局) 始める，決める 所有物／資産／財産s.

If your （米）棚上げする／（英）提議する needs four fields in each 記録，記録的な／記録する, you will fill in four 列／漕ぐ／騒動s of the datasheet. Don't let this disconcert you. Yes... fields are usually the columns of a datasheet. Don't let the layout in the （米）棚上げする／（英）提議する Design window 混乱させる you. The （米）棚上げする／（英）提議する Design window is not showing a datasheet 見解（をとる） of a （米）棚上げする／（英）提議する (列／漕ぐ／騒動s of 記録，記録的な／記録するs / columns of fields). It is showing the （米）棚上げする／（英）提議するs fields, one field to a 列／漕ぐ／騒動. The columns are pretty self explanatory, I hope, but let's go through them....

The first column is for is the field 指名する, which can be anything reasonable. I don't think you 許すd spaces in the 指名する. It would be best too 避ける them, in any 事例／患者. The 指名するs can be 事例／患者 極度の慎重さを要する. (I.e., if you call the field "演説（する）／住所", you can't subsequently 言及する to it as "演説（する）／住所", ADDRESS or "aDDRESS".) I said "can be 事例／患者 極度の慎重さを要する". The 支配するs for when they are and when they aren't are コンビナート／複合体. Make life simple for yourself: Work as if the 指名するs are always 事例／患者 極度の慎重さを要する.... and don't be lazy, don't everything lower 事例／患者. 指名するs like AddressFirstLine, and SerialNumber are 平易な to read. The 利益s far outweigh a little bit of 数字表示式の (as in fingers!) inconvenience.

The second column lets you select the data type for the field. (I have a whole tutorial on data, or field, types for you. It is an important topic, but if you want to leave it until later, then use the type "Text[VARCHAR]" for most things, and "Integer [INTEGER]" for things that you may want to do arithmetic with, e.g. numbers of widgets in 在庫／株. (With "Integer", fractions are not possible. If you need fractions, use "Real[REAL]"... but 避ける it if you can.)

You don't need to put anything in the third column, "Description". It's 役割 is obvious. It can be a good place to 供給する 指導／手引 for your 使用者s on the way you want data coded. For example, if the field is for a "yes" or a "no", but you have decided that this must be entered as "y" or "n", the description is a place where you can put that （警察などへの）密告，告訴（状）, and have it 現在のd to your 使用者s at the 権利 moment. If 使用者s hover over the 長，率いるing of a column, the description comes up as a tooltip.

Once you have 明示するd a field type, boxes appear at the 底（に届く） of the 審査する which let you 始める，決める さまざまな things. For now, the default values will be okay, unless you are told to use something special.

Some 罰金 points, some プロの／賛成のs and 反対／詐欺s ________

You must have a 最初の／主要な 重要な in every （米）棚上げする／（英）提議する. Often it is やめる 満足な 簡単に to use an integer which is automatically filled in for you, by ooBase. If you use the wizard to create the （米）棚上げする／（英）提議する, it takes care of creating such a 最初の／主要な 重要な. This field won't be "good for anything"... other than 供給（する）ing your database with the obligatory 最初の／主要な 重要な. It will give each 記録，記録的な／記録する "a number".... not "human friendly", but some 肉親，親類d of 最初の／主要な 重要な is needed by the computer.

If you are using the design 見解（をとる） to create the （米）棚上げする／（英）提議する, and you want an integer 最初の／主要な 重要な, it is still 平易な.

The 最初の／主要な 重要な should be in the first field. You can arrange that as follows:

If you already have some field 指名するs entered, and you have not yet left the （米）棚上げする／（英）提議する Design window for the first time, you can 挿入する a new 列／漕ぐ／騒動 by 権利-clicking, in the first 列／漕ぐ／騒動, on the gray box to the left of the "Field 指名する" column, and selecting "挿入する 列／漕ぐ／騒動". (If you have left the （米）棚上げする／（英）提議する Design window before seeing this, "play with" what you have, you may be able to 直す／買収する，八百長をする things... but if it doesn't go 井戸／弁護士席, you may find it quicker just to start again!)

指名する the field ID, or something 類似の. Make the field type "Integer". Use the 所有物／資産／財産 setting boxes at the 底（に届く） of the （米）棚上げする／（英）提議する Design window to turn on the "自動車-value" 選択, i.e. 始める，決める 自動車-Value to "yes". The system-供給（する）d "自動車-increment 声明: 身元" is 満足な.

Once you have 始める，決める up the field thus, 権利 click on box at the left 手渡す end of the 列／漕ぐ／騒動, and click "最初の／主要な 重要な". A little golden 重要な should appear in the first column. That's it. You're done.

A 詳細（に述べる）: You might be tempted to try to use a different data type for the 最初の／主要な 重要な. The only other type which 申し込む／申し出s 自動車-value (which is a 広大な／多数の／重要な convenience) is the BigInt type. The "Integer" type 許すs you 2,147,483,647 記録，記録的な／記録するs per （米）棚上げする／（英）提議する without getting clever. (Twice that if you do get clever.) This very generous 準備／条項 comes at the minor cost of a わずかに extravagant use of memory / レコード space. I 疑問 you'll ever have too many 記録，記録的な／記録するs for an Integer 重要な, and I wouldn't lose any sleep over the slight waste of memory / レコード space. If the size of the 記録，記録的な／記録する is 批判的な, and you are willing to sacrifice the 自動車-value convenience (or 供給する it for yourself some other way), and you know you won't have more than 32,767 記録，記録的な／記録するs then you can use the Small Integer data type... and save five "spaces" per 記録，記録的な／記録する.

The values in the 最初の／主要な 重要な for the different 記録，記録的な／記録するs in a （米）棚上げする／（英）提議する must all be different. There are times when you must 始める，決める up more 複雑にするd 最初の／主要な 重要なs. Will you need to soon? Probably not if you are just getting started with databases. There is more on 最初の／主要な 重要なs in other tutorials. One bit of "最初の／主要な 重要な cleverness" follows, and then we will move on.

Pretend you are setting up a （米）棚上げする／（英）提議する to 持つ／拘留する the 指名するs of some 従業員s. Pretend that you are going to keep the surname in one field, and the first 指名するs in a second field. Unless you are a very small 会社／堅い, the surname will not be suitable for a 最初の／主要な 重要な. As soon as you have two "Browns" (or other), you're in trouble. (All of the 記録，記録的な／記録するs must have something different in their 最初の／主要な 重要な fields.) If you can be 確信して that you will never have two 従業員s with the same 十分な 指名する, you could proceed as follows. (Of course, as soon as you design your database, foolishly, like this, you will find that a second "Joe Smith" joins the 会社／堅い... in which 事例／患者 you will have to cheat and 改名する him Joe2 Smith, or use some such dodge. Messy. And not the way to make an 従業員 feel valued.)

But if you "dare", or are working on something 類似の where you won't get two "Joe Smith's", then all you need to do is....

始める，決める up a first field called "Surname", and a second field called "FirstName".

Make your 最初の／主要な 重要な the combination of the values of the first and second fields, as follows...

You can 始める，決める up such a 最初の／主要な 重要な using the （米）棚上げする／（英）提議する 創造 wizard. It does the 職業 権利. Alternatively, in ooBase 見解／翻訳／版 3, at least, you can use the design 見解（をとる）. It will 許す you to select two fields (use 転換-click) and 指定する them as the 最初の／主要な 重要な. (A long time ago, with ooBase 2, and when I was いっそう少なく experienced, I had some trouble when I tried making multi-field 最初の／主要な 重要なs. The "with the wizard" approach worked even then, and I would recommend you 昇格 to 見解／翻訳／版 3, if you 港／避難所't already, anyway.)

Just before we move on, some advice: While there are times when you will have good 推論する／理由s for using multi-field 最初の／主要な 重要なs, in general, I would try to 避ける them. They seem to me to be a 広大な／多数の／重要な way to slow 負かす／撃墜する the 操作／手術 of your database. Of course, machines are so overpowered today you probably wouldn't notice the database struggling... but why introduce 複雑さs? And remember that the database that 作品 井戸／弁護士席 with 10 記録，記録的な／記録するs may be wonderful, but when you've 追加するd the other 500 記録，記録的な／記録するs, to make the database 現実に useful, as …に反対するd to a little toy with some 実験（する） data, you may find that it isn't as nimble as it was with 10 記録，記録的な／記録するs. When designers care about such things (as they must) they ask "Is it scalable?" I.e., can it be 規模d up, to 対処する with many 記録，記録的な／記録するs?

Once upon a time...

Once upon a time, I いつかs had a difficulties when using the （米）棚上げする／（英）提議する 創造 wizard. I 設立する that if, during the wizard's 死刑執行, I availed myself of the chances it gave me to change the 指名するs or data types of fields, then I いつかs had trouble at the end of the wizard when I clicked "Finish". To get around this, I began using the wizard only to "rough out" a （米）棚上げする／（英）提議する, 供給するing it with enough fields for my needs, but not 存在 fussy about the 指名するs or types of the fields. When the wizard had finished creating the （米）棚上げする／（英）提議する, I then opened it in the design 見解（をとる）, and changed the field 指名するs and types. After I'd done this a few times, I asked myself why I didn't just create the （米）棚上げする／（英）提議する using the design 見解（をとる） in the first place. I 港／避難所't had these problems for a while. Either I'm not doing something I used to do, or there was a "feature" which was アイロンをかけるd out. Even in the "bad" old days, I could always get the 職業 done.

編集（者）の Philosophy

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.

広告 from page's editor: Yes.. I do enjoy 収集するing these things for you... I hope they are helpful. However.. this doesn't 支払う／賃金 my 法案s!!! If you find this stuff useful, (and you run an MS-DOS or Windows PC) please visit my freeware and shareware page, download something, and 循環させる it for me? Links on your page to this page would also be 高く評価する／（相場などが）上がる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 . . . . .