Are you saying that if TOTAL 2 AMOUNTS is a negative value, the record is omitted from the found set as though the field were empty?
YES! Exactly. I can't get a found set to recognize it as a number at all.
Sorry I accidentally hit the "Best Answer" button.
What kind of field is it? Given the word total in its name, might it be a field of type summary?
Its not a summary field. Its a calculation result.
A field of type calculation or auto-entered number? Stored? Unstored? Global Storage?
Can you post the expression you are using for the calc?
Calculation, Unstored, just adding two other fields from the same table and record.
Then why are they unstored? While either stored or unstored should work for your find. Finds and sorts on stored calculation fields are faster.
Next question: What is the result type specified for this calculation? (There's a drop down in the specify calculation for specifying this.)
I'm getting all the info so that I can try to repeat what you are experiencing, but thus far this shouldn't be happening. You may have an issue with your file.
Unstored because if any data changes it needs to be updated. No drop downs on any of the fields involved.
There is nothing usual or really crazy about these 3 fields....They are very simple straight forward everyday bland fields. I'm just don't understand why it won't recognize a field that has something in it as...nothing...and then omits it.
Stored caclulations update automatically when a value in a referenced field changes. The only time you need to make them unstored is when they use something like a Get ( CurrentDate ) function in the calculation.
I agree that these are very straight forward fields, but I needed those details before I knew that for sure.
While it should not have been necessary to do so, I suggest changing the storage options to make this a stored calculation and turn on indexing at the same time. That may fix the issue for this particular field as the update involved may correct the problem.
When I try to change it to "Do Not Store..."
I get the following:
The calculation “TOTAL 2 AMOUNTS” cannot be stored or indexed because it references a related field, a summary field, an unstored calculation field, or a field with global storage.
Which I don't know why it thinks it connected to anything else except the two fields it's using to calculate. They are not summary fields.
UPDATE: ok..I found out that one of the fields had no indexing..I turned that off and it allowed me to turn off Do Not Store.
And then what results do you get? These changes affect field indexing and that may be enough to correct the glitch.
I also figured something else in my script when I looked back and found the script I was using was a duplicate that was not the same script I was editing. By fully backtracking and following the "line of sight" - found my error. Me very bad!!!
I double checked the script..and updated it...but here is what worked now.
It finds if and INVOICE has NOT been paid. (or exported in this case)
Then Omits all records that have no invoice no. yet and other things not yet entered...blah blah.
But yes...it exported the negative number "=(empty)"
Thank you so much.