>Jim,
>
>The view designer should throw up it's hands and give up without a fight if the view is too complex instead of handling it the way it currently does.
>
>Can you by chance post a version of the problematic view as a bug repro fragment so a fix might make it into Europa?
>
SNIP

David,

I don't really mind if it would "offer" to try to let me do it in the designer AS LONG AS it ALSO offered me a way to say 'no thanks, and goodbye'.

Here's an example of a view that will cause the problem I describe when you attempt to "MODI VIEW NoExit" after running the code.
WARNING: getting out of the designer will be difficult at best!

CLOSE DATABASES
CLOSE TABLES

DELETE FILE ViewProblem.dbc
DELETE FILE ViewProblem.dct
DELETE FILE ViewProblem.dcx
DELETE FILE T1.dbf
DELETE FILE T2.dbf
DELETE FILE TA.dbf

CREATE DATABASE ViewProblem

CREATE TABLE T1 (Fld1 C(10), Fld2 C(10) )
CREATE TABLE T2 (Fld3 C(10), Fld4 D )    
CREATE TABLE TA (FldA C(10), FldB C(10), FldX D )

CREATE SQL VIEW NoExit AS ;
    SELECT DISTINCT Fld1, Fld2  ;
        FROM ViewProblem!T1  ;
            INNER JOIN ViewProblem!T2 ON Fld3 = Fld1  ;
        WHERE Fld4 < ?dDate  ;
  UNION  ;
    SELECT DISTINCT FldA, FldB  ;
        FROM ViewProblem!TA  ;
            INNER JOIN ViewProblem!T1 ON Fld1 = FLDA  ;
        WHERE FldX = ?dDate  ;
        ORDER BY 1

cheers