>>I can narrow it down to 60 or so updatable fields, but does that do much? The only difference would be changing the statements to false, but it wouldn't shorten it. Or am I missing what you are getting at here?
>
>
>Ron, you got an error not from the view designer, but from UPDATE or INSERT clause that VFP generates when you try to save records. That SQL is generated behind the scene and you can't see it. For update it could look like this:
>

>UPDATE solidwaste!fac_mas;
>SET denrid_no = ViewName.denrid_no,;
>    sw_id     = ViewName.sw_id,;
>**** etc. All UPDATABLE fields will be listed here
>WHERE denrid_no = OLDVAL("denrid_no","ViewName")
>

>so that could exceed the SQL command length limitation
>
>
>>
>>Borislav, I'm a bit confused. Setting up this view like so has fixed my earlier problem, though given me a new one. Therefore, couldn't it be used productively? Or do you mean it is too much for what I am trying to do?
>
>What I meant is that you don't need that view at all.
>In how many forms you use it?
>A suggestion:
>BACKUP first your project (make sure you have a VERY good backup).
>Search ALL your forms where you use this view
>Then remove that view from DataEnvironment of these forms
>remove that view from database
>then go to each of these forms which used that view and just add the main table of the view solidwaste!fac_mas in DE.
>Set Buffering mode to 5 or 3 depending what was that value for the View. Set alias property to the same name as the view was and see how these forms will behave :-).

As in most other forums I would say

+1 :)