All the work I have done so far with VFP has been with tables, so I have felt pretty comfortable. Now I am taking a big leap into n-tier and using Visual Fox Express. My current project will need to be upsized to SQL server back end on a nationwide WAN, after version 1 is in production (so views not tables).

All the help and sample apps are simpler than my situation. The most common and most complex views involve only two tables. Usually the second is a lookup type relation. In the tables only world in 2.6 I would set up all tables that were needed to create my "Data Environment" for a form. Doing a view this way is obviously not the way to go, but I can't find any specifics on why. Is it more efficient to develop using simple views? Is it that the VD won't handle complex views, or do apps start to choke when there are 10+ tables in your view?

In the VFE tutorial several views are combined using a multiple cursor class but I havn't been able to find any explanations of the fundamentals involved in determining when a table is/is not brought in on the view level and when they are brought together in the multiple cursor class.

Brent