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- 12/18.

Data validation: Overview

Many times there are only a 限られた／立憲的な number of valid 入ること／参加（者）s for a given field in a （米）棚上げする／（英）提議する you have created. For example, if you have collected data on a group of people, and you have a 推論する／理由 to want to know each person's gender (and you are going to be "old fashioned" and only 認める two... please... can we proceed as if that would be 許容できる?) then you'll have a field which should only 持つ／拘留する "male" or "女性（の）", or some other pair of codes, e.g. "m"/"f".

Continuing with our example: It would not give a human any trouble if いつかs you 記録，記録的な／記録するd an individual as "male" and other times you 記録，記録的な／記録するd him as "man". Computers do not 栄える on inconsistency. It would be best if you used one and only one code for each gender throughout the database. （米）棚上げする／（英）提議する 強制s are one 道具 you can use to guard against 無効の 入ること／参加（者）s. I have shown how ListBoxes and ComboBoxes can help どこかよそで. In this essay, we 調査する （米）棚上げする／（英）提議する 強制s, which I 嫌疑者，容疑者／疑う are, in general, more 価値のある.

For this tutorial we will pretend that we've been given the 職業 of keeping 跡をつける of the 指名するs of the children …に出席するing a 確かな prestigious 搭乗 school where every child is a member of one of the に引き続いて "houses", (i.e. 内部の 部隊s of the school): Ravenclaw, Gryffindor, Hufflepuff or Slytherin.

Digression...

Since 令状ing this essay about using TABLE 強制s on data, I've become aware of another 道具. It is a little more 複雑にするd, in some senses, but I like it much better than either the contraints 課すd by ListBoxes, or the system discussed here. It is based on using foreign 重要なs. In a nutshell, if you 手配中の，お尋ね者 to 制限する the 入ること／参加（者）s to just, say 'rav','gry','huf','sly' (for our Hogwart's example), you would create a separate （米）棚上げする／（英）提議する with just four 記録，記録的な／記録するs, 持つ／拘留するing those values. You would then tell the school 名簿（に載せる）／表（にあげる） （米）棚上げする／（英）提議する ("HSL", in the 構成要素 that follows すぐに) that only something 設立する in the lookup （米）棚上げする／（英）提議する is 許容できる as a value for a pupil's house.

I have been struggling with these things for some time. さまざまな tutorials touch on the 問題／発行するs. So many, that I wrote a "sub-索引" for you of things that discuss what the "relational" means in the 称する，呼ぶ／期間／用語 "relational database"... the sort that is ありふれた today, not that you would know that they are relational, given the way some people use them. の中で them, I would commend the one in which I talked about such things in a tutorial about keeping 跡をつける of 株式市場 投資s.

If I were you, I would skip the essay you are reading, and go to one I wrote later, Using Foreign 重要なs to 改善する database 有効性，効力, which is, I hope, better. (I hope I am using "Foreign 重要なs" 適切に in that 肩書を与える!) You can always come 支援する here if you don't like that one! I like the technique explained in that, be "Foreign 重要なs" a proper 指名する or not, better than the one I talk about here.

For some comments about "Foreign 重要なs", I would 言及する you to a 文書 from Microsoft.

支援する to work... digression ends...

We'll build a simple （米）棚上げする／（英）提議する, 配分する "codes" to stand for the four houses, and create a 強制 which will 妨げる us from entering an 無効の value for the child's house.

The school 名簿（に載せる）／表（にあげる） database

(I believe I've also used this database in at least one other tutorial, apart from the one on ListBox and ComboBox.)

Create the database.

Create a （米）棚上げする／（英）提議する in it. Call the （米）棚上げする／（英）提議する HSL. (For "Hogwart's School 名簿（に載せる）／表（にあげる）")

In it, 供給する the に引き続いて fields:

ID integer, 自動車 value, 最初の／主要な 重要な
指名する, type Text(直す／買収する，八百長をする)[CHAR], length 30
House, type Text(直す／買収する，八百長をする)[CHAR], length 3

Create a form. You might 同様に use the wizard. (How appropriate!)

You only need a very basic form. 含む all fields, use "datasheet" 協定. Call it HSLwLookup for "Hogwart's School 名簿（に載せる）／表（にあげる） With Lookup". 出口 the wizard, electing "Work with the form" as what you will do next... even though you won't. After the wizard の近くにs, の近くに the form which will have just opened.

Don't put any data in the （米）棚上げする／（英）提議する yet. If you have entered some data, then make sure that no 記録，記録的な／記録する in the "House" field 持つ／拘留するs anything other than "rav","gry","huf" or "sly".

の近くに the form, because we are going to work on the database some more... but by a 大勝する which may be unfamiliar.

追加する 強制s

In the main 事業／計画（する） 経営者／支配人 window (the one with three panes, "Database", "仕事s" and another) click on the menu item "道具s", and choose "SQL". In the "命令（する） to 遂行する／発効させる" box, enter....

ALTER TABLE "HSL" ADD CONSTRAINT "House_List" CHECK ("House" IN ('rav','gry','huf','sly'));

... and you should get message...

"命令（する） 首尾よく 遂行する／発効させるd."

(If you don't get that, check the data in the （米）棚上げする／（英）提議する... if any 記録，記録的な／記録する has something other than 'rav','gry','huf','sly' in the "House" field, that... やめる 論理（学）上... will 妨げる the 命令（する） from 遂行する／発効させるing. 直す／買収する，八百長をする the 感情を害する／違反するing 記録，記録的な／記録するs. Try again.

We'll talk about what that does in a moment. Before we do, notice:

HSL is just the 指名する of the （米）棚上げする／（英）提議する we want to attach a 強制 to.

"House" is a field in the （米）棚上げする／（英）提議する. "House_List" is a way of 説 "the 名簿（に載せる）／表（にあげる） of 許すd values associated with the 'House' field". 'rav','gry', etc, are of course the 名簿（に載せる）／表（にあげる） of 許容できる values for the field, but notice the punctuation. どこかよそで we saw 引用するs ("s) and semicolons (;s).... now we have 選び出す／独身 引用するs ('s) and commas. Sigh.

In your own databases, you will use different things in place of the "HSL", and in place of the "House"... but the 残り／休憩（する） will stay the same, even the "_List".

A 詳細（に述べる）: I think the 指名するs are 事例／患者 極度の慎重さを要する, i.e. if you called the field "House", as I told you to, you can't 言及する to it as "house".

What have we done? We've 始める，決める a 強制 on the （米）棚上げする／（英）提議する. You can now の近くに the "遂行する／発効させる SQL 命令（する）" box and 再開する the form. Try to enter an 無効の value. Base will throw up a message box telling you....

"Error updating the 現在の 記録，記録的な／記録する. Check 強制 違反 House_List （米）棚上げする／（英）提議する: HSL in 声明 [UPDATE "HSL" SET "House"=? WHERE "ID"=?]

(Most of that, believe it or not, makes reasonable sense. It's a pity that the value you are trying to 割り当てる to "House" is 取って代わるd with the question 示す, and that the 記録，記録的な／記録する's ID is also 取って代わるd with a question 示す, but さもなければ, what you see is a taste of useful things to come.)

Just 認める the message, 直す／買収する，八百長をする the value, and all will be 井戸／弁護士席.

The （米）棚上げする／（英）提議する's 強制 has 誘発する／引き起こすd an exception event, and the database's default event handler has 答える／応じるd. I believe you could 供給する a different handler, one that would 現在の a more 使用者-friendly error message.... but that's another story for another time.

So far so good? I hope so. What I've 現在のd can have its uses. However, as I said at the 最高の，を越す... I am not 納得させるd that neither what's here, nor "constaint by ListBox" is 満足な.

Now I 恐れる this page unravels somewhat. As I said... I hope what I 現在のd is useable. But what follows will 明らかにする／漏らす some of my 疑問s about, problems with, this system.

The messy bits...

Here are some things that worry me when I use the technique 述べるd above, instead of using the foreign 重要な 強制 system which I 普通は use.

My questions/ worries...

Here's something I don't know how to do. Can anyone help? Is there a small tweak which would make that SQL 命令（する） say that the House field can 持つ／拘留する 'rav','gry','huf','sly', or be blank? I was hoping that something like...

... might be possible? (Email 詳細（に述べる）s at 底（に届く） of page.)

ALTER TABLE "HSL" ADD CONSTRAINT "House_List" CHECK ("House" IN ('rav','gry','huf','sly',NULL));

除去するing 強制s

I 地位，任命するd the に引き続いて in an earlier 見解／翻訳／版 of this page:

"Help? I would welcome advice on the に引き続いて....

"How can the designer 除去する a 強制 after
 it has been 適用するd?

"How can the database designer see what 強制s
have been 適用するd to a given （米）棚上げする／（英）提議する?"

I also 地位，任命するd the questions at the OpenOffice.Org 会議, and I soon had an answer from the marvelous Drew Jensen, who knows a lot about ooBase and is very generous in the time he 充てるs to 供給（する）ing answers to people at the 会議. Until the line "end of 構成要素...", the に引き続いて is ひどく based on what Drew wrote. Any useful stuff probably （機の）カム from him, but remember I've edited what he wrote, so problems may have been introduced which are not of his making!

(Start of 構成要素 mostly written by Drew Jensen)....

1) To 除去する a 強制 from a （米）棚上げする／（英）提議する, use "raw" SQL. I.e. Use use "道具s | SQL..." to 問題／発行する a SQL 命令（する） "by 手渡す". The に引き続いて, I hope, illustrates the 関連した 命令（する）:

(You would 取って代わる the HSL with the 指名する of your （米）棚上げする／（英）提議する, and the House_List with the 指名する of the 強制 you 手配中の，お尋ね者 to 減少（する）.)

2) To 追加する a 強制, Drew's method, using the Hogwart's School 名簿（に載せる）／表（にあげる） example 始める，決める up for this tutorial, again using "raw" SQL....

(That is very 類似の to what I had above...

ALTER TABLE "HSL" ADD CONSTRAINT "House_List" CHECK ("House" IN ('rav','gry','huf','sly'));

... but 異なるs in using "House_constraint" where I used "House_List". I'm not sure about the プロの／賛成のs and 反対／詐欺s. I believe either "作品" to 達成する what we 手配中の，お尋ね者!)

3) To 名簿（に載せる）／表（にあげる） the 強制s 現在／一般に active in a （米）棚上げする／（英）提議する, Drew knew of only one way to do it with an HSQL embedded database... which is what you have when you use OpenOffice's database without "getting clever".

You have to use the SCRIPT 命令（する）. With that, you can 捨てる the database to a とじ込み／提出する. You can then read the 強制s in that とじ込み／提出する.

To do that: 問題／発行する the に引き続いて SQL 命令（する）:

script 'c:\tmphsl.sql'

('c:\tmphsl.sql' is 単に where the 生産（高） is to be written. You can send the 生産（高） to a different place or use a different filename.)

Oh... Girl Scout Cookies! That worked, 以前. I'm now on a Windows 7 machine, and am getting "Exception: tmphsl.sql (接近 is 否定するd)". I've tried c:\tmphsl.sql and c:/tmphsl.sql, too... Still problems. Sigh.

(I think that's just a "simple" 事例／患者 of not trying to work 直接／まっすぐに with とじ込み／提出するs in the root directory. Create a folder there (perhaps a saga in itself), perhaps, say, C:\MyRoot\, and then do what you like in that. (Not 実験（する）d yet... let me know if it 作品 for you?))

The 命令（する） used to create a text とじ込み／提出する called c:\tmphsl.sql. The text とじ込み／提出する will 含む／封じ込める all of the DDL and DML 命令（する）s needed to 再構築する the database. When Drew did the above using an example database he had, part of what he got was.....

CREATE CACHED TABLE "config"("CompName" VARCHAR(250),
"ContactName" VARCHAR(150),"ContactPhone" VARCHAR(10),
"ContactEmail" VARCHAR(100),
"SalesName" VARCHAR(100),"SalesInitials" VARCHAR(3),
"InvoiceSeed" INTEGER,"LastSynch" DATE,
CONSTRAINT "silly_constraint" CHECK("config"."SalesInitials" IN ('atj','ATJ','silly')

You can see a 強制 he had 追加するd 近づく the end of the above, where it is a part of the "create (（米）棚上げする／（英）提議する)" 命令（する）.

Drew says that there is 現実に another way to check 強制s using the system （米）棚上げする／（英）提議するs in the HSQL database (and thus, also, ooBase, usually) at runtime - but the simple 捨てる and text search for the word 強制 is easier to do using Base - and besides he could not remember what the system （米）棚上げする／（英）提議する and column 指名する were when he was 令状ing his helpful advice.

(End of 構成要素 mostly written by Drew Jensen)

More help....

In July 07, I had two helpful 出資／貢献s from Will. The first was some comments on the question of knowing what 強制s have been 適用するd....

(Start of adapted 引用する from Will)

The SQL 基準 含むs a way to 陳列する，発揮する all of the （警察などへの）密告，告訴（状） about a particular （米）棚上げする／（英）提議する... you just "say"...

DESCRIBE "<TableName>"

... <TableName> 存在 the 指名する of the （米）棚上げする／（英）提議する you want the （警察などへの）密告，告訴（状） about.

Unfortunately, HSQL's (and thus ooBase's) database engine used doesn't seem to 器具／実施する this.... but the fact that a straightforward way to 陳列する，発揮する a （米）棚上げする／（英）提議する's （警察などへの）密告，告訴（状） 存在するs in some SQLs should serve as 激励 to others to search さらに先に for a way to do it in HSQL/ ooBase.

(End of adapted 引用する from Will)

I hope someone finds a better way to do it, and sends the （警察などへの）密告，告訴（状） to me! (Editor)

Please help 改善する this tutorial?

Question: I asked the に引き続いて question: How can I 直す／買収する，八百長をする things so that, say, the pupil's 指名する must begin with an H? A strange 必要物／必要条件, of course, but it would do to illustrate a 過程. I'm hoping something like.....

ALTER TABLE "HSL" ADD CONSTRAINT "指名する" LIKE ("H*");

.... is possible. Why? Because if it is, the idea can be adapted to, for instance, be sure that a social 安全 number fits the 基準 判型 (ddd-dd-dddd, where "d" is a digit)

Sadly, 10/12, Windows 7, OO 3.4.1, when I tried the above, I got...

1: 予期しない 記念品: LIKE in 声明 [ALTER TABLE "HSL" ADD CONSTRAINT "指名する" LIKE]

Answer(?):A 使用者 指名するd Will kindly sent に引き続いて, which I 港／避難所't 実験（する）d yet, but believe should work...

(Start of another adapted 引用する from Will)

To do this, you use a subset of "正規の／正選手 表現s". (The 称する，呼ぶ／期間／用語 used in the 狭くする sense used by computer people)

正規の／正選手 表現s in SQL are very 平易な:
Use "_" (強調する, not hyphen) to 示す a place where any one character goes,
or use "%" to 示す a place were one or more characters can go.

Thus, you had the query you asked about was done almost 正確に, just change the "*" to a "%"...

ALTER TABLE "HSL" ADD CONSTRAINT "指名する" LIKE ("H%");

To input US SSNs in your （米）棚上げする／（英）提議するs, use the に引き続いて 強制:

ALTER TABLE "<TableName>" ADD CONSTRAINT "SSNFormat" LIKE ("___-__-____");

<TableName> 存在 the 指名する of the （米）棚上げする／（英）提議する you want to alter.

Sadly, at least one source says that "_" and "%" are the only 正規の／正選手 表現s you can use in SQL.... you can't (maybe) avail yourself of all the other clever things that are possible with some of the 除外するd 正規の／正選手 表現s... and, as について言及するd above, at 10/12, my OO is 辞退するing to 認める "LIKE". Sigh.

I got this （警察などへの）密告，告訴（状） on the に引き続いて webpage (googled "sql 正規の／正選手 characters"), but there are plenty of pages that talk about it. The に引き続いて is good, but read the bit at the 底（に届く） of it, "SQL 正規の／正選手 表現s" first... Helpful SourceForge 令状 up about 正規の／正選手 表現s.

(End of adapted 引用する from Will)

Have you ever noticed how an answer just gives rise to more questions? I wonder if there's a way to say that the character must be a digit.... From my reading of Will's 出資／貢献, I believe that, if you 始める，決める up the second 強制, you would find the に引き続いて....

許すd:
052-64-1234 (a valid US SSN)
aaa-bb-cccc (not a valid SSN)

NOT 許すd:
052 64 1234 (hyphens 行方不明の)
052-64-123 (too short)

... not all of which is as we would like it, of course.

Here's the link to my eddress one more time, to make helping everyone 平易な for you!

More Good Stuff

Here are some more barely edited scavengings from the web 関連した to the above. This comes from...

http://www.oooforum.org/会議/viewtopic.phtml?t=167173&最高潮の場面=強制+data+入ること／参加（者）

ーするために 実験（する） the ideas below, I 追加するd a field called "YOB", for Year Of Birth, to the （米）棚上げする／（英）提議する "HSL". Data type integer.

Question: I am trying to 限界 the 範囲 on a numeric input on a form. I.e. if the 使用者 enters 2055 when the 範囲 is 始める，決める from 1950-2050 it will return an error so that I can 最小限に減らす data 入ること／参加（者） mistakes. I understand that this may need a SQL 命令（する）. Any ideas?

Answer: On the form level you can do this with a numeric 支配（する）／統制する which 許すs you to 明示する an 最小限 and a 最大限 (a "formatted 支配（する）／統制する" I think it is called.)

Below form level (e.g. （米）棚上げする／（英）提議する/query/update) you can still enter 独断的な numbers within the 範囲 of the data type.

Try this 命令（する）, using "道具s/ SQL" to 問題／発行する it....

(The 命令（する） has been "tweaked" to fit the Hogwart's example we've been working with. "HSL" and "YOB" would be different in a different 状況.)

ALTER TABLE "HSL" ADD CONSTRAINT "YOB_Limit" CHECK ("YOB" BETWEEN 1950 AND 2050)

(A 詳細（に述べる）.... Pedant, moi? The above ALLOWS 1950... but not, at least, 1949. 厳密に speaking, I wouldn't say that 1950 is between 1950 and 2010. Would you? I imagine some young programmer would tell me that I should "know what he meant". Sigh.)

You can 除去する the 強制 like this:

ALTER TABLE "HSL" DROP CONSTRAINT "YOB_Limit"

In HSQLDB such a 強制 is 限られた／立憲的な to the field values of one 列／漕ぐ／騒動. It can not do any comparison between other 列／漕ぐ／騒動s nor （米）棚上げする／（英）提議するs.

To make a 全く absurd 実験（する） 事例／患者, 追加する two more fields to HSL: FirstYear and SecondYear, both of type integer. Then 遂行する／発効させる the に引き続いて...

ALTER TABLE "HSL" ADD CONSTRAINT "YOB_Limit" CHECK ("FirstYear" <= "SecondYear")

Those fields make little sense in our database, but with the 強制 just 名簿（に載せる）／表（にあげる）d, we have a method to 要求する that any number entered into "FirstYear" of a given 記録，記録的な／記録する must be いっそう少なく than the number entered into "SecondYear" of that 記録，記録的な／記録する. Very useful in some 状況s. Just hard to create a 推論する／理由 to use that trick in the Hogwart's School 名簿（に載せる）／表（にあげる） example! Thank you Will!

公式文書，認める the わずかに strange 状況／情勢 適用するing: The 強制 is tied to the field YOB... which isn't 伴う／関わるd in the numbers we are 実験（する）ing! But the 強制, as written, does "work"... except... it doesn't "complain" if one or the other of "FirstYear" or "SecondYear" is empty. (You could "直す／買収する，八百長をする" this by making both fields be of the "入ること／参加（者） 要求するd" type... then the "失敗" of the 強制 would not arise. There's always some way to 肌 the cat... just be careful not to get too kludgy, won't you?)

編集（者）の 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. Deta8ils 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.orgMostly passes. There were two "unknown せいにするs" in Google+ button code. Sigh.

. . . . . P a g e . . . E n d s . . . . .