>Ken, if you're reading this, I think that in vfp 8, the VD should either be fixed COMPLETELY, neutered so it allows only one table per view (thus avoiding reliability issues altogether), or replaced with thorough documentation on how to create views as well as pointers to Erick and Steve's products.
>
>Alex

The View Designer can break single table views just as easily as multiple table views. One problem I often run into is when I add a field to the base table on SQL Server, then open my remote view with the intention of adding the field. If there are any data-type changes in the field properties, I have to set them back to their proper types.

This will invariably cause the fields further down in the field list to become corrupted. I see parts of the underlying SQL stuck in the default and message values like 'dbo.order.orderdate'.

I guess the only good thing about the view designer is that it works great as MS repellant. Any time you have a thread that has been infiltrated by MS talking heads, just mention the View Designer and they scatter like roaches running from the light.

- Keith