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 ソフトウェア, 3/06- 10/12.

Field Types, or Data Types

Consider a database to keep 跡をつける of people in an organization. A nice simple database, with just one （米）棚上げする／（英）提議する.

We'll 始める，決める up the に引き続いて fields...

• ID: Just a 天然のまま number... see below
• 指名する: 指名する: See below
• DOB: Date of birth
• YrJoined: Year joined organization
• StillWith: Still with organization

Many of the above, and many of the choices below are oversimplified to 避ける unnecessary 複雑化s. Unnecessary to our 目的 of 調査するing "what is a 'data type'?" Don't worry about "井戸／弁護士席, that wouldn't be any good..." type questions... here... please?

ID: For the 目的s of our discussion, each person within the organization will have an ID which will be just a number. The number will "belong" to one person for evermore; it will not be "re-cycled" if, say, person "0251" leaves, and a new person comes along afterwards. (The new person will not be given the "now 解放する／自由な" 0251.) (Of course, turning people into numbers is obnoxious, and I wouldn't do it in the real world, but just for this example, we'll do it.)

In database work, in every （米）棚上げする／（英）提議する, there must be a field where for every 記録，記録的な／記録する(ShrtDef) what is in that field does not arise in any other 記録，記録的な／記録する. The （米）棚上げする／（英）提議する must have a "最初の／主要な 重要な", and the field used for this must be thus.

(There are ways to produce a 最初の／主要な 重要な from a combination of fields... but that's for later! (With a 最初の／主要な 重要な made by "構内／化合物ing" (連合させるing the values in two fields) you could have a 非，不，無-unique value in one, as long as the result of the combination is unique の中で all the combinations 現在の in the （米）棚上げする／（英）提議する.))

指名する: For our discussion we're going to put the whole 指名する in one field, e.g. "Smith, Joseph".

YrJoined: This will just be something like "2009"

StillWith: Still with organization: Here we will have "y" or "n"

Setting up the database

Whether you 始める，決める up the （米）棚上げする／（英）提議する using the "Create In Design 見解（をとる）" (my 推薦) or with the "Wizard", you are going to have to 生成する a 名簿（に載せる）／表（にあげる） of the fields for each 記録，記録的な／記録する, give them 指名するs, and say what the "Field Type" will be. Depending on the field type, there will be other specifications to decide.

"Field Type" is more 一般に called "Data Type", in my experience of things computery. Try both if you go to Google.

Why the hassle?

You are asked to 明言する／公表する the field type for each field because if the database "knows" the field type, it can optimize both the 貯蔵 要求するd and the 過程ing. It can also help you 避ける bad 入ること／参加（者）s in your （米）棚上げする／（英）提議する.

A very simple database program, much cruder than Open Office's Base, might 申し込む／申し出 just two field types: "number" and "text". Even that would be a start. If the database knew that a field was of the "number" type, it could 拒絶する "Fishcakes" as 容認できない, if you tried to put that value in the field.

Open Office Field Types

The 幅の広い 部類s of data types 利用できる to you are:

• Types for strings of characters, be they letters, digits, other
• Types for dates and/ or times
• Types for numbers
• Special types

That's one way of 配合 the types... and probably the most important way to do it.

You could also 分裂（する） all of the types into these two 部類s:

• Variable length types
• 直す／買収する，八百長をするd length types

This discussion will not be exhaustive... there are types which I won't explain here.

The two most important types for strings of characters are Text(直す／買収する，八百長をする)[CHAR] and Text[VARCHAR]. In each 事例／患者, you will 明示する the 最大限 number of characters to be 許すd for values 蓄える／店d in the field.

We would use one or the other for our "指名する" field.

I believe that the difference between the two is that if you use the first, and 明示する that the longest 許すd string is 28 characters long, then on the disk, each 記録，記録的な／記録する will have 28 bytes of space 始める，決める aside for this field. You will be able to enter shorter strings. In the 事例／患者 of the latter, if the first 記録，記録的な／記録する has "Smith, Joe" in it, and the second has "Metcalf-Gibson, Alexander", then if you've used Text[VARCHAR], only ten bytes of your disk's space will be used for Joe, but 25 will be used for Alex. Has to be good, yes? 井戸／弁護士席... yes and no. Good for disk space efficiency, but the database may be able to 過程 the （警察などへの）密告，告訴（状） more quickly if every field's datum is of the same length. Hence さまざまな data types, so you can choose something to 会合，会う your needs!

We'd use Text(直す／買収する，八百長をする)[CHAR] for the "Still With Organization" field, and 始める，決める the length to 1. There are also ways to say to the database "only 受託する a "y" or an "n" in this field".... but that's not part of the data's type

The "text" data types give you 広大な／多数の／重要な 柔軟性.

If the field "only" needs to 持つ／拘留する a number, though, use an appropriate type. You may or may not want to avail yourself of the special types for dates and times. Another approach to them is separate simple numeric fields for "year", "hour", etc.

Moving on, looking at "simple" (my 称する，呼ぶ／期間／用語) numeric types, the first big divide is "integers"/"非，不，無-integers"... in other words, "whole numbers", or numbers with fractions. If you can do your 職業 with integers, use them. (いっそう少なく 複雑にするd for computer... so faster, and some 半端物 problems 避けるd.) I いつかs 記録，記録的な／記録する cash 人物／姿／数字s inside the computer in pennies, so as to 避ける having to use fractions. It also 速度(を上げる）s data 入ること／参加（者）, once you are used to "seeing" $21.98 as 2198.

Computers, as you know, work (mostly) in binary; we work in decimal. Hence some things that seem strange.

Once we've decided we're only 利益／興味d in integers, the next 決定／判定勝ち（する） is "調印するd or not 調印するd?" In other words: Do you need 消極的な numbers?

によれば http://wiki.openoffice.org/wiki/Base/Data_Types, if you don't need 消極的な numbers, and you only need 0-255 (which makes sense, if you go into the binary/decimal 問題／発行するs), then you can use the TinyInt [TINYINT] type, and 蓄える／店 the data using only one byte of disk space per datum. The （米）棚上げする／（英）提議する designer dialog says you will use three bytes. Sigh. There are five data types you can use for 蓄える／店ing integers. BigInt[BIGINT] lets you 蓄える／店 integers from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807... but it takes 8 or 19 bytes, depending on who you ask.

その上の help with field types

That's not "everything" about data types... but enough to give you what you need, I hope? If not, I 申し込む／申し出 a more 広範囲にわたる discourse on field types (data types) as used in Open Office.

編集（者）の Philosophy

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.)

広告 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.

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 . . . . .