Hi Paul Hutchinson and James Caska,

I did not want you to think I was an ingrate -- sorry for the long delay in
responding, but I owe you a 'thank you' for your replies. All I can really
report now is a sincere thank you to both of you -- both of you had some
very good ideas and code that was more elegant than mine.

Trying to help myself and possibly others in this thread, I'm still hung up
in VB.NET. I just wanted to compile that *simple* VB6 'toy' project that I
posted here a few messages back as a ZIP file. I'm still stuck, and need to
spend more time on it. It's one of those typical engineering things where
"it should be simple". I guess I have zero brain cells today. :)

I'm not really asking anyone to help or spend time on this, since it is my
problem, but I thought I should post some details out of courtesy to your
replies:


> What you probably want then is simply this..
>
> .NET  ==================================
>
> 	Dim bytUART_Byte As Byte
>
> 	bytUART_Byte = MSComm1.Input()(0)
>
>  ==================================
>
> This is the same as
>
> VB6 ==================================
>
> Dim byteArray() As Byte
> Dim bytUART_Byte As Byte
>
>     byteArray = MSComm1.Input
>     bytUART = b1(0)
>
>  ==================================

As far as that VB.NET line you suggested does not compile:

   bytUART_byte = MSComm1.Input()(0)


Build error: Option Strict On disallows late binding.


Just as a quick experiment, I used the VB.NET upgrade wizard to convert that
'toy' VB6 code project I posted earlier as a ZIP file. I figured it would be
an easy program for the upgrade wizard to convert, but no luck so far.

VB.NET compiles the 'MSComm1.Output = Chr(lngCount And 255)' line without
error (using Option Strict On, Option Explicit On), but when I run the
program, I get the following error:

   Error 380 - Property value is not valid

So, I'll have to go back to drawing board to see why the MSCOMM output
method is not working for me. Like you mentioned earlier, it looks like I'll
have to dig into the encoding/decoding conversions you mentioned previously
(and other suggestions in this thread). Everything in that 'toy' VB6 project
seems to work ok except for the MSCOMM's 'Input' and 'Output' methods, so
it's *very* close. Like I said, I do have a solution with the Sax control,
but I would like to resolve this and place the information in this thread
for the benefit of others.

Thanks again for your time and for your help James and Paul -- I definitely
appreciate it.

Best regards,

Ken Pergola








_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist