![]() While check box sets have their appeal, storing more than one value in a field violates First Normal Form (each “row-and-column intersection” should contain exactly one value), and if we want to report on this data, we will first need to clone it into a separate “tasks” table. At right you can see how the data is stored behind the scenes. This is not an argument I will be getting into today.)Īs you probably know, check box sets allow users to insert one or more values into a text field, and assuming multiple values are inserted, each will be separated by a hard return. ![]() ![]() (Of course it can be argued that one simply should not, under any circumstances, store data in text fields formatted as check box sets. But I have good news: Magic Key can help alleviate that pain, as you will see if you download and explore today’s demo file, magic-key-check-box-reporting. ![]() There are pros and cons to this approach, and one of the cons is that data stored in this manner can be a pain to report on. Have you ever built or inherited a system with data stored in text fields formatted as check box sets? I believe that the name originates with European developer Ugo Di Luca, and we’ll get to the details in a moment, but first let’s look at a scenario where it might come in handy. Today we’re going to look at a technique called Magic Key, which allows you to flexibly create and populate related records. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |