>Hi All,
>
>I'm using some of DBI's controls, ctExplorer for example, and have been quite satisfied with it. The latest suite contains a calendar control that I'd like to add to my app, but I can't get a handle as to how I should set up the tables. 31 fields in a table and 1 record per month, 12 records per year per user in one table, or should I split it up into two...three? Is anyone familiar with this control, and can you offer any suggestions as to how the the data set should look?
>Thanks.
>
>Luke
Having 31 separate fields for what is basically the same type of data is a huge nuisance. Just imagine searching for information in 31 different fields. For example, to find all information that happens to be on a Monday, or everything that happens on any date between 10:00 and 12:00. Or sorting such information. To be able to do any reasonable data manipulaton, you need to have each entry in a separate record, as Craig suggested.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
