Erik,

>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.

Someday I'll probably need to get around in a wheelchair, with a catheter, but I'm not getting fitted for them today. Don't _burden_ yourself with something you don't currently need.


>I have yet to implement a full client server app, but I know that I will have to in the future, and I know that some current clients will eventually need to move to a more secure database than VFP can provide. Since I use only views in my forms, I am ready.

Why not develop a transport object that allows dozens of identically formatted DBCs -- for multiple datasets -- to move the data to/from the backend. This allows you users the speed of VFP native and security/size of Oracle/Sybase/SQL Server. This allows the DBC to act as a "view" for many users, rather than each needing their own. The middle tier -- transort object -- not only performs validation, but also only needs a single client connection, rather than your way whicj would require a connection for each user. More at http://www.temperedsys.com/UFACS.htm

>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...snip

In the real world prepare for users _thinking_ they know what they want and then changing their minds!


>>For lookup tables I issue a straight SQL in the Init (or ReQuery if the contents are based on the value of another control).
>
>Try this with MS Access data on the back end.

I wouldn't dream of it!