>Fabio,
>
>What's the real USE CASE for wanting to be able to create a CursorAdapter that doesn't match the data store? It seems to be far more problematic than useful.
>
>If you make a CA field nullable but the base table doesn't support it, now the CA can't push the data back to the data store where the rows have null values in the field.
>

A little example:
- backend have a id IDENTITY (-2^32+1,1) PRIMARY KEY
- then id it is not a updatable field
- but when i INSERT a record into the VFP client's cursor,
which number I insert in the id.

For being corrected I MUST write a id that it does not exist on the backend, but all the id can exist, the only one that sure do not exist it is NULL.

However, who writes a development package,
does not have to only develop based on the examples that succeed to think, but must develop for abstract categories.
(this remembers to me when I taught,
and the greater part of the students did not reason for semantic categories, but it tried to assemble with of examples).

If the Team allow a CursorSchema for the CA local cursor,
therefore a code writes that allows the developer to define one its logic, even if this logic seems not to have sense
(every thing that is not understood seems not to have sense).

Fabio
Fabio