VB6 MSCOMM wroks on one PC and not another

[cooksydesign]

Again, thanks for the interest in my post. Changing the receive length property to 1 did not do any good. I think that tells MSCOM buffer what to expect. If the incoming string was a fixed length it may have helped. I seem to have sorted it out by sending the string to a label first, then work with the data. It has not failed since I started doing it that way. I realize this is a work around, and the true cause is not identified. If there are other suggestions, I will most certainly try them.

Regards.

B

[mister_e]

I no longer use MsComm and VB6, i use VBExpress or .Net. From there you can also use the LF interrupt events (comport.ReadLine) which is probably the way to go. Never ever failed for me 'till now. VB6 EOF event is one method... if you can make it work.

LF event... way easy to code on the PIC side... hserout [whatever, 10]

There's a lot of different way to have success with VB, i have some applications dealing with MBs and GBs of data transfer... problem-free since years now. Even in VB6.

I prefer the handshaking method... hardware or software.... and a preamble string never bite anyone yet.

[tenaja]

The new Visual Basic.NET 2008 is so much better than 6 that you shouldn't waste your time trying to get it to work.

[T.Jackson]

Incidentally, I just discovered that Microsoft has continued support for VB6 until the 31st of march this year. They initially terminated support back in 2005, there is obvioulsy still a considerable amount of programmers developing in it. Also, all of the latest operating systems come shipped with VB6 run times! (bet ya didn't know that) This includes Vista.

Expect to be able to run all of your VB.com applications on operating systems well into the next decade! VB6 is far from finished.

[T.Jackson]

The new Visual Basic.NET 2008 is so much better than 6 that you shouldn't waste your time trying to get it to work.

It's a very painful transition from VB.com to VB.net, particularly for programmers with 10+ years background with .com (like learning to walk all over again) and a lot of people are refusing to exchange their expertise for a "start from scratch experience", because that's pretty much what it is.

[T.Jackson]

lol ..
VB6 pro sells for upwards of AU $250 on eBay while .net goes for as little as $75.

[T.Jackson]

VB6 Pro US $229
http://cgi.ebay.com.au/Microsoft-Vis...sid=p1638.m122

VB.net 2003 $79
http://cgi.ebay.com.au/MICROSOFT-VIS...sid=p1638.m122

Both obsolete products which are officially no longer produced. VB6 was released in 97, so that's 6 years between the two, yet VB6 is worth more than 3 times as much. I have actually seen VB6 going for much more than this, as high as US $1,000

Makes you wonder huh?

[mister_e]

Well, probably because there's a lot of free version like EXpress and people just don't buy .NET ?

On the other side, there's probably more .NET to sale than VB6.. but more code in VB6 available for free...