Richard,

There is a known bug with the View Designer in handling complicated views. Complicated usually meaning more than 2 tables. You can do one of two things.
1. Create the view progromatically
2. Create a view of 2 of the tables and then create a second view based on the first and the third table.

I would suggest the first as there is more room for mistakes with the second when using in a form and managing TABLEUPDATE()'s and so on. HTH

>I put 3 tables into the view designer, all related via the Order_ID field.
>Selected some output fields, and set my conditions: Order not closed;
>OrderItem not closed; Supplier 400. I ran the view with no problem. I saved the view with no problem.
>
>So why, when I try to close the View Designer does it complain that
>"SQL: Column 'Order_ID' is not found" ????
>
>Below is the code the VD generated...
>
>SELECT Orders.order_id, Orders.last_name, Orders.first_name,;
> Orders.mid_name, Orders.suffix, Orders.dob, Orders.ssn, Orders.race,;
> Orders.gender, Orderitems.report_id, Orderitems.city, Orderitems.state,;
> Orderitems.county, Orderitems.country, Location.type, Location.name,;
> Location.address1, Location.address2, Location.city, Location.state,;
> Location.zip, Location.county, Location.country;
> FROM ofax!orders INNER JOIN ofax!orderitems;
> INNER JOIN ofax!location ;
> ON Orders.order_id = Location.order_id ;
> ON Orders.order_id = Orderitems.order_id;
> WHERE EMPTY(Orders.close_date) = .T.;
> AND Orderitems.sup_id = 400;
> AND EMPTY(Orderitems.closed) = .T.