Hi Simon,

>Just out of interest why was it designed this way as opposed to having Insert, Delete and Update methods?
>

In majority of scenarios, custom update is done by sending custom command to the back-end (in Native case, executing custom SQL-INSERT/SQL-UPDATE/SQL-DELETE). Having CursorAdapter to call an extra method in those scenarios would be an unnecessary overhead.

>Am I correct in assuming that you should always use "Native" as the Datasourcetype whem using custom InsertCmd, DeleteCmd and UpdateCmds?
>

If you want to run native code, the ...DataSourceType should be "Native". If you want to run custom back-end specific command through ADO or ODBC, for example, a stored procedure call, the ...DataSourceType should be set appropriately.

Thanks,
Aleksey.