>Hi Fabio,
>
>This is exactly how it is supposed to be. To display CursorAdapter on DE surface, the CursorSchema property should be set to a correct value, it is used to determine cursor's schema at design time.
>
>>OBSERVED:
>>when you put a CA into a DE,
>>you have to set the CursorSchema to 2 word,
>>

>>NULL NULL
>>bla bla
>>....
>>

>
>Not just to two words but to a correct CursorSchema value. When the type literal doesn't match any supported type, VFP uses first letter. Therefore, 'NULL' is reduced to N and 'bla' is reduced to B, which makes both values acceptable and equivalent to "NULL N", "bla B".
>
>
>>IF you go into the scx table,
>>remove CursorSchema line on Properties field,
>>reopen the scx:
>>2 errors and you have lost the CursoAdapter member!
>>
>
>Fabio, you haven't lost anything. The CursorAdapter is no longer displayed on the design surface (thanks to yours destructive actions), but it is still there. You can drill down to it in the Properties window and make necessary modifications or whatever you wanted to do.
>
>
>>update: another error:
>>on SCX properties field definition i found:
>>

>>CursorSchema = F1 C(10)
>>

>>expected it is
>>

>>CursorSchema = "F1 C(10)"
>>

>>
>
>By design, custom properties, properties not bound to a specific type and properties supporting very long values (CursorSchema is just one of them) are handled specially.
>
>
>>For Aleksey:
>>have you read:
>>Thread #968819
>
>The NULL should be casted to a proper type.
>
>>Thread #969403
>>Thread #969465
>>Thread #969475
>
>Didn't have much time for a thorough investigation. All of them look like a behavior well known for a long time. For a cursor in row buffering mode, VFP fires implicit TABLEUPDATE() when it has to or when it thinks it should. You have to account for that when you write your code.
>
>
>>Thread #969502
>
>Replied on the thread.
>
>Thanks,
>Aleksey.

Aleksey, the impression is exact, for time problems and ability you are defends to you on your positions, also when evidently they are mistaken.

Now, is useless that I lose ulterior time to discuss incoherent operations.

The shipment of mine completed issues/bugs ends here.

If I will continue to use VFP,
I will find of the workarounds that they allow me to continue,
otherwise I will change dev product.

You can calmer living now.

Regards
Fabio