Al,
Glad it helped. VFP6 definitely fixes many problems that VFP5 had, just make
absolutely sure you use VFP6-SP3, since VFP6 has many C5 crashes.

-Ed

>Thanks for the tip, Ed. The problem does seem to be in the REPLACEs (I need to do 33 columns). If I do just a few, it seems to be OK.
>
>I tried out MS's proposed workaround - according to MS, setting the view's WhereType property from 3 to 1 will let the update work properly. I did this immediately before the REPLACEs in a form method, then set it back to 3. Didn't fix the problem.
>
>The better "fix" seems to be upgrading to VFP6, which according to MS doesn't have this problem. I'll probably be doing this within the next couple of weeks... I'll see how it goes.
>
>>Since your using VFP5, there is a MS KB Article (Q169367) that I had
>>when I ran into a similar problem. You basically can't update more
>>than 23 columns in a grid with a certain update type. The article has
>>a workaround.
>>
>>
>>
>>
>>>
>>I'm using VFP5.0a (build 415). I've got a view-based form that creates a parameter object using SCATTER...NAME and passes it to another (modal) form (which uses a private datasession).
>>>
>>>On returning from the modal form, I'd ideally like to issue GATHER...NAME to update the view form's fields with updated values from the parameter object. However, if I try, I get the above error.
>>>
>>>If I try to REPLACE just a few view fields from the parameter object, it works. If I try a REPLACE of all, or slightly more than half, same error.
>>>
>>>When the modal form is closed, the .Activate of the view form is eventually called, which refreshes the view form. The error handler is reporting the problem in a piece of code that works perfectly in every other circumstance and which contains no SELECT - SQL statements even approaching the limit.
>>>
>>>The view-based form is fairly complex. Has VFP been known to throw bad/misleading error messages when the going gets tough?
>>>
>>>Any help or wild-assed guesses greatly appreciated.