>Keep in mind that in VB, complex logic can also be encapulated in class definitions as well...

But can these class definitions be subclassed?

In my VFP base classes I have the data controls determining, from the value that they are bound to, what the Picture clause should be. This works for every application that I write.

I am now working on a customer application with a particular data format, and I have a subclassed that definition to work with the help system that is specific for that application. With this help system, the Init method of these controls loads the help from a specific table. This help drives things like the ToolTipText (which the customer is free to change). Since it looks for help text from a specific table, it can't be made generic, unless I add properties & other code that will be ignored in _every_other_ application.

As far as SPT vs. Remote Views, BTW, I am a fan of neither. I prefer to retrieve the information using SPT, then create updateable cursors to handle the updates. This gives me the ability to work with the local cursors, as I have done for years, retrieve _exactly_ the data that I want without worrying about a finicky view definition, run stored procedures any time they are required (like to change a password), and log in to the server using true native SQL Server security, instead of some bastardized or open version that is required for views.

Now don't take this the wrong way. I'm not {directly) saying that VB is lousy. In fact, there are a lot of things that I would prefer to use VB for. But when it comes to writing database applications -- VFP will win pretty well every time.