>>Hi,
>>
>>Now that I have a couple of customers using my VFP application with SQL Server database I ran (once in a while) into a problem with NULLs. Here is what happens. In many places in the program the code creates an empty cursor. And then this cursor is populated from other cursors retrieved from SQL Server. And when adding a record to the initial empty cursor and a value happens to be NULL, the program bombs with an error (column COLNAME does not allow NULLS). In order to eliminate this issue I am thinking of always specifying/allowing NULL for every column of the empty cursor. Just in case. Will it slow down the processing of this cursor? The cursor usually is not very big, maybe up to 2000 records. What do you think? TIA.
>
>If you uses SQL language, NULL is everywhere ( every OUTER JOIN, aggregate function, ... can return NULL )
>
>Then NULL is the first knowledge sql step.
>
>Speed is not a issue.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
