SBPro4
2 messages in this thread
Another one of those 'moved from 3.0 and works fine until you try to change
it' problems: calculations for a field are much less tolerant in 4.01. I
have a calculated field that is a lookup based on another field. The
calculated field is one byte numberic and the lookup/tenery operator
defaults to " " if no corresponding record is found in the lookup file.
This still works, but if you try to edit the calculation, it won't allow it
to have the default " ", instead gives error message 'Field Requires
Numeric Data'. The clincher is that changing the " " default to 0 won't
work either! I guess the tighter edits (reads 'I won't let you be as
sloppy in your coding anymore') is great, but agravating: It is making
transition from 3.0 to 4.01 very painfull.
Follow on note to my previous message regarding 'less tolerant'
SBPro4/Amiga: I have since done some reorganization of the file in question
to take advantage of VIRTUAL fields for some super-descriptor fields
(compound calulated fields used as indexes for specific applications) and
found that I was able to correct the calculation IF I MADE THE CHANGE
BEFORE I GOT THE ERROR MESSAGE!! Seems to be a bug in the calulation
requestor, once it sees a logical error it may not be resetting the error
flag.