>So,
>why there is a option to do it?

Hi Ricardo,

The option is there because, sometimes, information about timestamp field is available. For instance, it is available when a remote view is attached to a CursorAdapter (I believe this is the only scenario). It is available for remote view because CREATE SQL VIEW command parses SQL statement, tries to determine what base tables are involved and checks what field is a timestamp field in each base table, this requires multiple round trips to the backend server. The information about timestamp fields is then stored into DBC and available internally when the view is opened. Neither CursorAdapter nor SQLEXEC are trying to do that advanced parsing mainly due to performance reasons and information about timestamp field is not available when they are used to create a cursor.

Thanks,
Aleksey.