>>Because Decimal will implicity widen to Double. You won't lose information but might lose precision. If I worked with VB.NET the first thing I'd do would be to set OPTION STRICT ON. It still allows all the implicit widening conversions but will catch a lot more potential problems at compile time
>
>When doing that, I obtain over 102 errors. Those are all with loRow() lines such as:
>
>
> ' Scan all records
> For lnCounter = 0 To loDataProvider.nCount - 1
> loRow = loDataProvider.oRows(lnCounter)
>
> ' If we have a shop
> If loRow("NoMember") > 0 Then
>>
>This is valid code. Why is the compiler complaining now with strict on?
(haven't been following thread - just looking at this code)
Not sure why the compiler would care, but could loDataProvider.nCount ever be 0 ? or loDataProvider ever be null?
For lnCounter = 0 to - 1 ( I think a step 1 is implied )
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
