On Thursday 09 April 2009, Jeff wrote:
What is the thinking behind a Result.MoveFirst() and MoveNext()
returning a false if a record is there?
So, to read round a result set I end up using a Boolean with a double
negative:
noMoreRows = myResult.MoveFirst()
WHILE NOT noMoreRows
PRINT
Ron_1st ha scritto:
On Thursday 09 April 2009, Jeff wrote:
What is the thinking behind a Result.MoveFirst() and MoveNext()
returning a false if a record is there?
So, to read round a result set I end up using a Boolean with a double
negative:
noMoreRows = myResult.MoveFirst()
WHILE
On Thursday 09 April 2009, Jeff wrote:
What is the thinking behind a Result.MoveFirst() and MoveNext()
returning a false if a record is there?
So, to read round a result set I end up using a Boolean with a double
negative:
noMoreRows = myResult.MoveFirst()
WHILE NOT noMoreRows
But during the long years now I have written programs :-) I found that we
most
often test for errors than success. So using TRUE for errors leads to less
lines of code.
It is just a matter of habit. And changing habits is a good thing, it keeps
you young. :-)
I need something to
