>>Views are not stable in intricate situations. Probably, this is one of them. The feasible (there other ones) workaround is following:
>>1. Make view based on just one 'trips' table, or you can even use just this table itself (no view at all).
>>2. If I remember right, you want to bring the data into grid. So, you make Grid.Recordsource="trips"
>>3. You have two columns which should show data from two other tables, and you set custom controlsources for these columns:
>>Grid.ColPickup="Thisform.SetCustomColumn(trips.pick_up)
>>Grid.ColDropoff="Thisform.SetCustomColumn(trips.drop_off)
>>4. Form.SetCustomColumn method
>>LParameter nLocationid
>>Select Location
>>Set order to tag lockey && it's faster to use SEEK() function here
>>Seek nLocationid
>>Return Location.Loc
>
>So no views this time? (sigh)
>
>Thanks,

Ed's suggestion wil definitely work, but I wouldn't give up just yet. I have a lot of view many times more complicated than the one you described, and I have yet to run into anything that I couldn't get around.

As David mentioned, there is a known bug woth the view designer that causes the error you describe. The error is with the view designer, not with views themselves.

Creating readonly views with code is a snap, just use the syntax David posted. It gets more indepth if you want to be able to update from your views, because there are several properties that need to be set with DBSETPROP. The manual details these, but IMHO, the best way to get a feel for what is needed is with gendbc.prg.