Re: Wish I was using .net
- From: "MikeD" <nobody@xxxxxxxxxxx>
- Date: Sun, 19 Feb 2006 18:42:27 -0500
"Michael C" <nospam@xxxxxxxxxx> wrote in message
news:OcDNSpZNGHA.964@xxxxxxxxxxxxxxxxxxxxxxx
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.
You can't blame this on VB. GetNewConnection is apparently not returning a
reference to an ADODB.Connection object. It it were, you'd have gotten a
Type Mismatch error (I tested it to be sure). So, it's YOUR fault and ONLY
your fault (or whoever the programmer was). There's no excuse for this bug
not to have gotten discovered during testing.
As to "Wish I was using .net", well....use it then and quit your bellyaching
about VB6. <g> Other than ranting, what was the purpose of your message?
--
Mike
Microsoft MVP Visual Basic
.
- Follow-Ups:
- Re: Wish I was using .net
- From: Michael C
- Re: Wish I was using .net
- References:
- Wish I was using .net
- From: Michael C
- Wish I was using .net
- Prev by Date: Re: how to print to pdf?
- Next by Date: Re: VB - Too weird to be true
- Previous by thread: Re: Wish I was using .net
- Next by thread: Re: Wish I was using .net
- Index(es):
Relevant Pages
|