Hiya Ken,

The View Designer can't handle complex joins (more than two tables) accurately and blows the view if you try to edit it from there. The best thing to do is to keep PRG's around with the CREATE VIEW AS and DBSETPROPS() applicable to the view and make your changes there, rerunning the PRGs as required to tweak settings.

As Bruce pointed out, Erik Moore has posted an excellent substitute for the View Designer, called eView.


>I am working with some legacy VFP 5.0 code, and have run across a problem in unis a local view.
>
>The view is updatable and contains three tables A, B , and C. Table A and Table B are joined by "Table A Left Join Table B". Table A and Table C are joined by "Table A Left Join Table B". There is no relationship between Table B and Table C.
>
>In the form using the view a structural index is built (INDEX ON ... TAG...) and used for ordering view on the screen.
>
>My problem is that I need to modify this view. When I open the view designer with this view, I receive a message that the index file for this table is invalid and I need to recreate the index. (Error message is paraphrased). When I click the OK button on the error message I am presented with the View Designer.
>
>When the view designer comes on the screen only Table A is visible and the list box for the selected fiels is empty. The SQL statement is intact and contains all fields, tables , etc.
>
>I have removed the view from the container and rebuitl it from scratch. I get the same results. After repeating this at least 100 times I am now convinced I will not be able to beat the code into submission and that the view is inherently screwed up. What am I missing?
>
>
>Ken Wardwell