Roman,

You saw in the help section that Error 1491 says the 'Table' property of the View is not set.

=DBSETPROP('myView','VIEW','Tables','myDBC!myTable')

But if that's not it, then I'd try defining the field property for UpdateName with the DBC syntax included, - 'myDBC!myTable.myfield' instead of leaving off the DBC.

Wally

>Hi
>
>My problem is that my view won't save changes, despite I think that have
>taken all the required steps to do it. First, no one is using the DBC and its
>tables (which is not necessary), all the fields of my view are updateable,
>table buffering =5. This is the first it happens to me, the only slight
>doubt I have is that I set updatetype=1 (u can't find much info about it
>in the documentation), which I believe is not the problem.
>The only solution I can think of is to reinstall VFP, but maybe you
>could help me to solve this before I do something unnecessary and not learn
>something new.
>
>Here is more or less How I've created the main view:
>
>CREATE SQL VIEW 'MainView' AS SELECT cursor.ID, cursor.padre,;
> view.descripcion FROM DBC!view INNER JOIN;
> Cursor ON view.tipo+view.cod+view.ID=cursor.tipo+;
> cursor.cod+cursor.ID
>
>
>and the select of secondary view was defined thus:
>
>SELECT table.id, table.tipo, table2.descripcion;
> FROM DBC!table2 INNER JOIN DBC!table ;
> ON table2.tipo+table2.cod = table.tipo+table.cod
>
>The error number I get from aerror() is 1491, could be that using
>a cursor created at runtime and establish it as table source of the
>view be causing this problem?
>The properties of the fields of the cursor are defined like the fields of the
>secondary view, except that in the propertie updatename I just use the name of cursor without defining a DBC for it.
>
>The view works just fine, it reverts changes too!, it's just won't save.
>
>TIA