Hi Fabio,

>EXPECTED: The CA must respect the declaration made in CursorSchema.

What is the ground for your expectations? Is it documented that NULL/NOT NULL are respected?
The nullability of the column is determined from the data source.

Thanks,
Aleksey.


>Previous issue Thread #967985
>
>Bug/Issue : 27 of 49
>
>TITLE: BUG : CA ignore the NULL declaration on CursorSchema property
>
>VERSION: 09.00.0000.1720 and previous
>
>EXPECTED: The CA must respect the declaration made in CursorSchema.
>
>OBSERVED: NULL and NOT NULL are not used for create the cursor.
>
>REPRO:
>

>#DEFINE  (local)
>CLEAR
>WITH CREATEOBJECT("session")
>  SET DATASESSION TO .DatasessionId
>  SET MEMOWIDTH TO 300
>  SET MULTILOCKS ON
>  H=SQLSTRINGCONNECT([DRIVER=SQL Server;SERVER=SERVERNAME;DATABASE=tempdb;Network=DBMSSOCN;Trusted_Connection=Yes])
>  IF m.h>0
>    TRY
>      IF SQLEXEC(m.h,"CREATE TABLE #CATestTable (id INT IDENTITY PRIMARY KEY,fName MONEY NOT NULL)")>0
>        WITH CREATEOBJECT("CursorAdapter") as CursorAdapter
>          .DataSourceType ="ODBC"
>          .DataSource    = m.h
>          .BreakOnError  = .T.
>          .Alias      = "CATestTable"
>          * BUG : CA CursorSchema ignore the NULL declaration on CursorSchema
>          .CursorSchema  = "id I NULL,fName Y NULL"
>          .SelectCmd    = [SELECT * FROM #CATestTable]
>          .CursorFill(.T.)
>          LIST STRUCTURE
>          * NOW: CAN I INSERT A NOT DEFINED ID ???? any integer is a defined id, and 0 it is too !
>          INSERT INTO CATestTable VALUES (NULL,NULL)
>        ENDWITH
>      ENDIF
>    FINALLY
>      =SQLDISCONNECT(m.h)
>    ENDTRY
>  ENDIF
>ENDWITH
>