Just keep in mind that you really have two options.

The first is to use the Foxfire! view, which I wrote about.

When you use the Foxfire! "alternate views" option, there is a field in each Data Item definition and each Relationship Definition where you can create and name an alternate view. What makes it somewhat elusive is that uses a "compliment" approach, where in you create the view by specifying what you DON'T want included in the view.

Here's how it works: In the Data Item Editor, in the "Advanced" form, there is a Views/Groups section. The "Views Excluded field is where you define the view implicitly (as opposed to explicitly). Each Data Item in which you enter a view name into that field will be excluded from that view. So if you named that view in 3 different items, the view would actually consist of all items except those three. 

In the Relationships Editor, there is also an advanced tab where you can block a particular relationship from a view. The field is called "Exclude relationship from the following views"

So by implicitly building a view of "everything less the omitted items", you can create one or more alternate views.

I don't know why it works that way - it's been in Foxfire! over 10 years since v3 and my only guess is that our customers felt it was easier to eliminate the items you didn't want than to construct a view of items you did want, since you must type the name of the view in each item.

I keep thinking we should create a View editor that functions similar to the Data Item Group Editor where you could use an explicit approach of dragging the items and relationships you wanted into a view. But I can see that with a large database (many tables, fields and relationships), the "compliment" approach could be considerably faster.

Finally, there's the other way of accomplish views: using a different Report Set for each view. It's permitted (and often done that way) to have more than one Report Set point to the the same system files - Requests, Data Items, Relationships, etc. So for each view, you define a Report Set pointing to the same System files.. But you use the System Files form of the Report Set Editor to specify a Report Set Filter in the Data Item, Relationship, and Request files. Then you add those values into the Data Item and Relationship definitions of those elements you want to include or exclude in the view (depending on the filter condition you entered in the Report Set definition). In the Data Item editor, that field is in the same Views/Groups section of Advanced form, and it's called "Report Set Filter Values." In the Relationship Editor, it's called "Report Set Filter Values.  

I'd appreciate hearing how you feel about these methods, or whether you some other form would be more effective, as we are very interested in hearing how our customers find working with our product, both in front of the screen and behind it.