In certain cases there is another option: use the raw tables under role aliases and define the views in terms of these role aliases. This avoids hard-coding paths (or, even worse, DBC names) into views. How you define these aliases does not matter except that the names must not match any existing tables or views anywhere (because in that case Fox could quietly use a stray physical table/view that it finds in the path, instead of complaining that nothing is used in a certain role).

In our company we have a rule that table/view names must not start with a character followed by an underscore because such names are reserved for internal use (like X_* for role aliases, Z_* for #defined table names etc).