Subtitles of the Movie

Let us complete our tour of the define database dialogue by looking at the options for storage. There are 3 sets of storage options. You may never need to adjust these but if you do need them you should know what they are. The first is global storage now global storage breaks the relational model in this way. Normally in a table you have rows and column of data with one row or one record for every person or object that is in the database and field has one value per row. Global storage says that for this field there will be one value per table, not per row and if I put this field on to a layout I will see this same data in every single record because it is indeed the same data in every single record. If I change the value of global storage in record one, I will change it in record 2 and record 10 and record 10000 because it is the same value. It is global. Now why would you do this? The two most common cases in which you would do this are first of all if you want to use a global field to display some help or some information you could type it onto the layout but you could also put it into a field and putting help text into a field is sometimes easier to maintain because it is easier sometimes to maintain a field than a layout. So, the help information would appear on every layout where that field is present. You also when use calculation may need temporary storage for variables counters and loop for example and global values are very useful at that point. Repeating fields, now in the relational model you have seen how we can use a relationship to how an infinite number of telephone numbers or addresses for someone. But there are certain types of values where it is useful to say that a field contains a certain number of repetitions. For example you can specify a color using 3 numbers that identify the amount of Red, Green and Blue in the color. This is called an RGB value. So an RGB variable could consists of 3 fields Red , Green and Blue or it could consists of filed called RGB that has 3 repetitions and you would know that repetition one is Red, repetition two is Green, repetition three is Blue. What is valuable about this is instead of 3 fields you have one field that creates a logical entity and it is a very efficient use of repeating fields. Well, repeating fields are not good is where you find yourself with pairs of them. So, for example let us say I have repeating field with 10 repetitions for 10 telephone numbers and next to that I have another repeating field with 10 repetitions for telephone number types. So repeating field 3 of the telephone number is telephone type 3 of telephone types. That is the relationship. When you start pairing repeating fields you are definitely in the world of relationships. That is what you should be using but if the data intrinsically has 3 values or 2 values or 5 values or 10 values then using repeating is very efficient way of working. Finally come down here to indexing and the most frequently chosen option is this one. Automatically create index is needed if everything around FileMaker will do what it wants to. You can prevent it from indexing a field or you can use 2 types of indexing and for this I need to explain to you very briefly how FileMaker indexes data. It creates value indexes and word indexes. Value indexes can be created on any type of field except the container field and value index basically consists of an index of the field data. Technically it is an index of the first 100 characters of each line of the field's data, so if you have a field with 5 lines separated by carriage returns you will have 5 value entries in the index because there are 5 lines separated by carriage returns. And it is only the first 100 character that are indexed and this provides indexing for searching and joining and works very efficiently. A word index takes a text field only a text field and indexes every single word in the text field. No hundred character limitation on a word index for a text field and that is why when you saw the searching you will see cases you are searching on entire word in beginning of word that is running of word index. Now what happens if you say automatically create indexes is needed the first time you do a find, particularly on a text field you will have a delay as the appropriate index is being built so if you know, you are going to be doing certain finds on certain fields and you do not want to have this delay the first time people do those finds on those fields one of the things to do is to say automatically create index is needed and do the find yourself before you let other people use the database the first find will take much much longer than subsequent finds. Or you can say I want to create these indexes automatically but in general the best case is to say none but create some if you need them and finally you can choose the default language for indexing and sorting text and what matters here is the Unicode option. The Unicode option treats every character separately. The language options treat upper and lower case and certain other characters as identical so normal indexing in English does not matter where capitalization is. If you do want capitalization to matter choose Unicode as the language.