Wednesday I encounted a bug where a query that ran with the value set to -1 for years... stopped working in every query. I had to change everything from -1 and 0 to true and false, has this happened to you?
Wednesday I encounted a bug where a query that ran with the value set to -1 for years... stopped working in every query. I had to change everything from -1 and 0 to true and false, has this happened to you?
Never, they are all the same:
yes/no
-1/0
true/false
if anything, -1 would work and true would fail.
I know right? If anything it should have been the opposite. Reverse big endian returning memory leak from hell I guess.
Curious as to what this means.stopped working in every query.
0 is always false. True is anything else.
Maybe somebody changed a comparison somewhere from (e.g.) x <> 0 to x = -1 (or x = 1) ? The former is better because, as I said, 0 is always False.
Something had to change to cause the 'failure'. Methinks even a windows update could cause it.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
This happened to me years ago and if memory serves me correctly it was because the Backend was upsized and -1 which is True in Access was not so for the Backend but True was True no matter what backend I upsized to or what language I was coding in. So, I just switched to True. Okay, that doesn't explain why it suddenly broke... just food for thought,