Re: Wish I was using .net
- From: "Lance Wynn" <LanceWynn@xxxxxxxxxxxxxxxx>
- Date: Sun, 19 Feb 2006 19:50:47 -0700
Oh,
Then I have to agree with MikeD, that's just the way the language is. In
..NET, or any language for that matter you'll find a number of runtime errors
that for whatever reason the compiler won't catch. It has nothing to do
with the language, or the compiler. There are a number of instances in VB
where you wouldn't want the compiler to raise an error at compile time if
there were a potential type mismatch. If you don't catch something in
testing, then you don't catch it, that's how every language works.
Lance
"Michael C" <nospam@xxxxxxxxxx> wrote in message
news:ewYtbNcNGHA.344@xxxxxxxxxxxxxxxxxxxxxxx
"Lance Wynn" <LanceWynn@xxxxxxxxxxxxxxxx> wrote in message
news:%23ysif%23bNGHA.916@xxxxxxxxxxxxxxxxxxxxxxx
Can you post some code samples, I too cannot get this to compile. Having
a
function return a connection, and trying to set that to a command object
gives me a type mismatch at runtime. I am interested in learning under
what
circumstances this can occur so I can avoid it if I come across it.
That is what it is meant to do. The point is you get it at runtime, not at
compile time like it should.
Michael
.
- Follow-Ups:
- Re: Wish I was using .net
- From: Michael D. Ober
- Re: Wish I was using .net
- From: Michael C
- Re: Wish I was using .net
- References:
- Wish I was using .net
- From: Michael C
- Re: Wish I was using .net
- From: MikeD
- Re: Wish I was using .net
- From: Michael C
- Re: Wish I was using .net
- From: Lance Wynn
- Re: Wish I was using .net
- From: Michael C
- Wish I was using .net
- Prev by Date: Re: empty GUID from string in VB2005
- Next by Date: Re: Wish I was using .net
- Previous by thread: Re: Wish I was using .net
- Next by thread: Re: Wish I was using .net
- Index(es):
Relevant Pages
|