I wonder if a simple change could be made to allow autofind to find a blank
code record.
The change in 12.1 to use rowid logic made this task a little more
difficult.
We often have code files with two fields. Code and Description
In these files we have a blank code and a description such as "Not used" or
similar.
Autofind eq fail to log on becuase it fails in the procedure Item_Find in
data set
in the following extract.
If (not(IsNullRowId(riRow))) Begin
Move True to bChanged
End
Else Begin
// or, if the record was already changed or the entry_update
created a change
// we consider this changed
Get_Attribute DF_FILE_CHANGED of iFile to bChanged
End
bChanged is never set true when the field being looked up is blank.
The work around I use is to trigger
Move "A" to field // required for something different than "" to set
DF_FILE_CHANGED
Move "" to field
I tried to set item changed but that does not set DF_FILE_CHANGED which
only appears to be set true when a value other than the present value is
moved to a field
What i think would be good is to have another test in the bChanged logic
above to trigger an autofind on
a boolean field such as pbAllowBlankFind in a form which a user could set.