Well alright then. It's time to move a little further in our explanation of what Tableupdate() does.

What VFP does behind the scenes on a Tableupdate() is to generate a SQL statement to actually update the record. If you look on the Update tab of the View Designer, you'll see 2 sets of radio buttons to set how the SQL statements are generated. If you have the option set for the "SQL WHERE" to include the key field and ALL updateable fields, the Where clause of the SQL will contain a Table1.Column1 = View1.Column1.....and Table1.ColumnN = View1.ColumnN. So if your table includes a sizeable amount of columns you can make the SQL statement too long.

If you are using VFP 5 there is no simple way around that I'm aware of. If you are using VFP 6 you need to use the SYS function Jim Nelson described.

PF

>Perry,
>
>Thanks for the reminder. I checked Aerror() and it's saying "Query is too complex." But I'm not trying to do a query at that point. All I've done is changed the text in one field. I wonder if it's just too many fields -- but that just doesn't feel right. I mean, if I'm understanding the way the class is written, it just goes through each of the tables and if it finds one in which fields have changed it attempts to overwrite the old information with the new. So, since I've only changed one field, I'm not sure how that could be "too complex."