OK. We all know and have read and seen for ourselves that in a client/server environment the "old" navigation, i.e. VCR back/forward/top/bottom, is not practical.

But let's leap pver that for a second, and assume that we have a project where that type of navigation is an absolute requirement. (Do not waste your time responding that I should convince them otherwise.)

The question is the best approach to bringing down the data for the main navigation screen. Lert's assume we have SQL Server like this:

tableMain1 - - - |
tableMain2 - - - -| -- these 3 tables combine to form the view that we must navigate thru. initially 10,000 records but could grow to a million rows
tableMain3 - - - - -|

Then that view has a one->> and one--> relationship with 7 tables. However each of those 7 tables need to potentially display on the master navigation screen, with 0-50 child records in each of the 7 tables

What do the wise people here think would be the best approach?