When planning the data component of any particular application, we always start with a data model. A data model is just a diagram or description that defines the record types and their relationships. These record types, or models, will closely map the types of data we expect to bring into the application. So, for instance, if we are going to load student record data, we will likely want a
Let's look at an example of how a data model for a calendaring application may start out:
This data model is about as simple as it can get. We have calendar records, each of which has zero or more event records. In turn, ...