I have two text elements bound to Date fields on the same layout. When I get the values from both the fields and both of them are empty by the following code.

vRSHandle = @XResultSetSearch(@FN, "Index", SEARCH_MODE_AND, SEARCH_SYNTAX_QA, "!RecNumber=" + RecNumber)
     if(vRSHandle > -1)
     {
                 ResultsetCurrentPosition (vRSHandle, 1)
                             
                 vLastLead = @XResultSetValue(vRSHandle, "Last_Lead")
                 WriteLN ("Last Lead Level = " + vLastLead )
                                               
                 vLastLab = @XResultSetValue(vRSHandle, "Last_Lab")
                 WriteLN ("Last Lab Done = " + vLastLab)

           XResultSetClose(vRSHandle)
     }

vLastLead = 0000/00/00
vLastLab =      (Null)

If I place some date in both the elements, both of them retrieve the values properly, only the different behavior with Null value.

What make them inconsistent? Properties of both the elements and fields are identical and both belong to the same database and layout. Computer actions are seldom random, what make them to behave differently? Which one is the expected behavior and which one is aberrant?

Please help me to understand this. Thanks.

I looked into it further to find out what is rule and what is exception. Here is what I found.

vLastLab = @Xlookup (@FN, RecNumber, "Tracker!RecNumber", "Last_Lab")
WriteLN ("This is the date value for Blank Last_Lab: " + vLastLab)


vLastLab = @Xlookup (@FN, RecNumber, "Tracker!RecNumber", "Last_Lead")
WriteLN ("This is the date value for Blank Last_Lead: " + vLastLab)


vLastPap = @Xlookup (@FN, RecNumber, "Tracker!RecNumber", "Last_PapDate")
WriteLN ("This is the date value for Blank Last_PapDate: " + vLastPap)


vLastMammogramOrderDate = @Xlookup (@FN, RecNumber, "Tracker!RecNumber", "Ordered_Date")
WriteLN ("This is the date value for Blank Memmogram Order Date: " + vLastMammogramOrderDate)


vDTaP5 = @Xlookup (@FN, RecNumber, "Immunization!RecNumber", "DTaP5")
WriteLN ("This is the Date value for Blank DTaP5: " + vDTaP5)

vMMR2 = @Xlookup (@FN, RecNumber, "Immunization!RecNumber", "MMR2")
WriteLN ("This is the Date value for Blank MMR2: " + vMMR2)

The Slate display following results:

This is the date value for Blank Last_Lab:
This is the date value for Blank Last_Lead: 0000/00/00
This is the date value for Blank Last_PapDate: 0000/00/00
This is the date value for Blank Memmogram Order Date: 0000/00/00
This is the Date value for Blank DTaP5:
This is the Date value for Blank MMR2:

It is 3 and 3 even.  They are very consistent in the results - meaning the same field gives the same result when performed repeatedly.  Only thing that might differ as to when the fields were created. I have been using Sesame from version 1.0 to 2.5. I believe the newly created Date field gives Null results but I could be wrong in my this assessment.

Quote:


All the variables used are the string variables.  like

var vLastlab as String
var vLastLead as String

Quote:


From some fields String Variable is getting empty string while from other it is getting "0000/00/00/" and that seems to be the problem.

Quote:


The date values were initialized by the programming generally.  Since the value is blank in the external database from which value is retrieved, it was not initialized, I suppose.

I believe the newly created Date field with version 2.0 and after gives Null results while the fields created with earlier versions is giving "0000/00/00" string to the string variable for the blank value but I could be wrong in my this assessment.