eView gives me the same error message and so does maintaining the view in code.

that is it chokes on the first line :

CREATE SQL VIEW "SUBMOTOR" ;
AS SELECT * FROM motor WHERE Motor.equip_id = ?equip.eqno

DBSetProp('SUBMOTOR', 'View', 'UpdateType', 1)
DBSetProp('SUBMOTOR', 'View', 'WhereType', 1)
DBSetProp('SUBMOTOR', 'View', 'FetchMemo', .T.)
DBSetProp('SUBMOTOR', 'View', 'SendUpdates', .T.)
DBSetProp('SUBMOTOR', 'View', 'UseMemoSize', 255)
DBSetProp('SUBMOTOR', 'View', 'FetchSize', 100)
DBSetProp('SUBMOTOR', 'View', 'MaxRecords', -1)
DBSetProp('SUBMOTOR', 'View', 'Tables', '')
DBSetProp('SUBMOTOR', 'View', 'Prepared', .F.)
DBSetProp('SUBMOTOR', 'View', 'CompareMemo', .T.)
DBSetProp('SUBMOTOR', 'View', 'FetchAsNeeded', .T.)
etc ...

Does anyone know what compiled line is too long?

>Don-
>The view designer is limited. It's not a robust tool. IOW, except for basic views, it chokes. You can either maintain the view in code, or Erik Moore uploaded a utility called eView (I think) that is an enhance view designer. You might want to try that.
>
>HTH
>
>...snip
>>
>>However if I need to make a change to the view I receive the "Compiled code for this line is too long" error message. In a clever move it prevents me from opening the veiw at all. I have to create the view from zero everytime I need a change.