>This is a general
>This is the interpretation made from the VFPT.
>
>My interpretation is of general type:
>
>In a language that supports the NULL,
>whichever function with all the null parameters must give back:
>- or a predefined value
>- or NULL
>
>Put NULL on a optional parameters or not put a value on it, is equal.
>
>In fact
>

>? DATE(null,null,null)
>? TIME(null)
>? DATETIME(null,null,null,null,null,null)
>

>are correct.
>
>Example:
>

>* these simple VFP functions not support NULL
>? ADDBS(null)
>? QUARTER(null , null) && but WEEK(null,null,null) yes
>? EVALUATE(null)
>? ALIAS(null)
>? SELECT(null)
>? SYS(null)
>? FKLABEL(null)
>.....
>

>
>For me, SQL Server support NULL.
>
>On SQL Server exists a native function that not support all NULL parameters ?
>
>Fabio


Hi Fabio,

I would say that support for NULL is documented as: The functions that accept NULL values as parameters should propagate it to the result.
And VFP does that. The functions that do not accept NULL as parameter generate errors.
If in SQL Server all functions support NULL parameters, then all SQLServer functions should propagate NULL to the result.