I second John Koziol's input. Use a view and use code to create the view. Code like this...

CREATE SQL VIEW v_Companies AS ;
SELECT ;
Companies.*, ;
Lup_Description as CompanyType ;
FROM ;
mi!Companies ;
left outer join mi!Lookups on Cmp_TypeLupFK = Lup_PK ;
WHERE ;
Cmp_PK = ?lcCmp_PK ;
and Cmp_TypeLupFK = ?lcCmp_TypeLupFK ;
and Cmp_Name = ?lcCmp_Name ;
and Cmp_ID = ?lcCmp_ID

=DBSetProp( 'v_Companies', 'View', 'UpdateType', 1 )
=DBSetProp( 'v_Companies', 'View', 'WhereType', 3 )
=DBSetProp( 'v_Companies', 'View', 'FetchMemo', .T. )
=DBSetProp( 'v_Companies', 'View', 'SendUpdates', .T. )
=DBSetProp( 'v_Companies', 'View', 'UseMemoSize', 255 )
=DBSetProp( 'v_Companies', 'View', 'FetchSize', 100 )
=DBSetProp( 'v_Companies', 'View', 'MaxRecords', -1 )
=DBSetProp( 'v_Companies', 'View', 'Tables', "MI!Companies" )

=DBSetProp( 'v_Companies.Cmp_pk', 'Field', 'KeyField', .T. )
=DBSetProp( 'v_Companies.Cmp_pk', 'Field', 'Updatable', .T. )
=DBSetProp( 'v_Companies.Cmp_pk', 'Field', 'UpdateName', 'MI!Companies.Cmp_pk' )

in a little program which you can run as often as you need to while you are working out the specific implementation of the view.

Not only does this get around not being able to fix the complex views in the designer, it also allows you to copy all the DBSetProps into any new view-making programs.