Wish I was using .net

I just got an bug report from a customer and found the problem was something
like this:

Dim c as new ADODB.Command
set c = GetNewConnection ' function that returns a new sqlserver connection

The last line should have read "set c.activeConnection = GetNewConnection".
Now I'm going to have to do a new build and go through all the hassle of a
release (there's quite a few steps to this now). Undoubtedly this got out
due to human error however c# or vb.net wouldn't have even let this line of
code compile because it knows straight off that a connection object cannot
be set into a command object. It's amazing how many similar errors it picks
up like this while working. Many of those errors would be picked up fairly
quickly but some will get through.

Michael




.

Quantcast