We have seen how easy it is to create tables and their fields using the two respective grids of the FieldView form. There is one more thing this form lets us create though.
As we have mentioned earlier, the Tables grid is a two-level grid. The top level lists tables, while the second level lists InfoView forms belonging to each table.
Each InfoView in Alventis is considered to "belong" to its respective main table. Relational InfoViews may "bring together" data from more than a single table, but one of these tables will be considered "main", so even these complex InfoViews can still be deemed attached to a single table. We will be talking about Relational tables and InfoViews in another chapter, but we just wanted to make sure you understand the overall relationship between tables and InfoViews.
Any table may have more than one InfoViews (or none at all, of course, but that would be a little sad). All InfoViews of a table are listed in the second-level sub-grids underneath the table. The columns of these InfoView grids are almost entirely self-evident, so we'll rush through them quickly:
You create a new InfoView – you probably guessed by now – by creating a new record in the grid. Delete the InfoView by deleting the record. Nothing to it.
Once you have created a new InfoView record, you may open the corresponding InfoView form by double-clicking the record or hitting Ctrl-Enter on the keyboard. The new blank form with the Caption you have specified is created for you. You can now put some fields and other interesting stuff onto it, but this is the subject of the next chapter.
It may be a bit premature to tell you this, but it seems most appropriate at this point, so we'll tell you now. An empty InfoView you just created is truly "very empty". You may have created it under the Contacts table, for example, but in its empty state, it has nothing that "bonds" it to this particular table. It is only when you start placing fields onto the InfoView (well, creating Controls corresponding to some fields, really, but we'll allow ourselves to use such imprecise language), so, it is only at that point, that there's something in the InfoView that really establishes a strong link between it and some table. Therefore, whichever field you place first on an InfoView determines what table this InfoView will be "representing" – that of the field you just placed. Usually, you'd obviously place the fields of the table for which you created the new InfoView onto it, so all of the above won't be an issue. But if you make a mistake or just change your mind, and start with a field of some other table, the InfoView will get re-assigned to that other table. This may only happen to an empty InfoView with no existing fields, so InfoViews won't be "jumping around" too much.