For a view, VFP generates a SQL statement which you won't see, to update the underlying table. I think that perhaps if you change the update properties of the view to "key fields only", the resulting "internal" SQL statement will be much simpler.
This should be more efficient in any case, than the default option.
>Hi all,
>
>I have a view in a form that updates a table with 100 fields. The SQL statement is short, as all the fields belong to one table but 2 of them.
>
>When I issue tableUpdate(.t., .f., 'myView'), I get the error "SQL string is too long", and return .F.
>If I force all rows to be updated with tableUpdate(.t., .t., 'myView'), then I don't get the error.
>
>I don't even know how to debug it to know what's happening inside, and why the error goes away when I force the update.
>
>Any ideas?
>
>TIA,
>Javier.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
