I checked all these to no avail. Then I started looking at the view again, I did not have the checkbox
marked in the UPDATE tab of the view for SEND SQL UPDATES. Not sure what this REALLY does but
through trial and error testing (see I do test!!!) it works now.

Thanks


>NOW you're getting into less specific territory.
>
>You're using a view, right? Is the table underlying the view loaded? Is it buffered? If it IS buffered you have to do a tableupdate() on the underlying table as well to save it to disk.
>
>Are you running the TableUpdate() on the right view? If you haven't SELECTed it or called it explicitly you may be updating a random lookup table you didn't change < grin >.
>
>Next, if it's a new record, you may be having trouble with the key. If your key is assigned only when you save the record to the table, then your data may not be following along. (This is a problem when adding records only)
>
>Finally, set a breakpoint at your TableUpdate() command and check the underlying data. Actually look at the data in the table as well as the view before/after the update.
>
>HTH
>Barbara
>
>>Yea, I know, I know... I forgot all about the quotes - I tried all the other ways. Can I ask you one more ques...
>>
>>is there any logical reason why the loop works, the TableUpdate(.T.) returns a TRUE, but the records in the
>>DB don't update? The view has key & modified fields, SQL update and the qtystart, qtyend are marked.
>>
>>Once again, thanks for all your help!!!!