>Josh supporter #1 here. Jim- if your app is operating on local data on a fast network with little concern for network traffic and absolutely no shadow of a chance for C/S upsizing in the future, then tables are fine. But I think you've missed the major point about the huge advantage to using views in all other scenarios. If Josh's app uses strictly views (even for lookup tables), then he can switch to remote views without changing a single line of code in his forms.
>

Bingo!

>Once you are familiar with the techniques needed for view-based forms, they are really just as easy as table based forms. There is not really any more work to it, just different work. The client server mentality is based on the premise that the user has an idea what he wants to see before he sees it, and in the real world, there is not much need to look at a list of 10,000 names in alpha order to decide which record to look at.

Give the boy a ceeeeeegar :0

>>For lookup tables I issue a straight SQL in the Init (or ReQuery if the contents are based on the value of another control).

Or use a grid's recordsoucetype as 4 - SQL and stuff the recordsource property with a string built based upon the interactive change event of a textbox gathering lookup parameters.