>>Two weeks ago, I was working on a form having an updatable view. At that
>>time, I was still designing the form. While testing the form, suddenly, I
>>had an error. After the error, I found that the value I entered in an
>>updatable field in that view had been reflected to the entire table. Which
>>mean, all the records in the table suddenly had a value of 30 for that
>>field.
>>
>>Now, that is something. Anyone has already seen something like that?
>
>Happened all the time while I was working via ODBC to Excel sheet,
>anytime when there was a collision in field structure or the phantom 'No
>update tables specified. Use the Tables property of the cursor.' error.
>Take a look at the other thread ("SQL Pass-Through with 'Memo' fields"),
>I've put the details there.
>
>There seems to be a serious problem (bug?) in the behavior of views
>defined programmatically - they seem to work fine most of the time, but
>once you get any kind of error, it starts behaving in most unimaginable
>ways.

It seems to be related to development time problem. In production, once that is all debugged, it works ok.