Re: Has Microsoft Stopped Revising VB Components?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Bob Butler (tiredofit_at_nospam.com)
Date: 12/01/04 

Date: Wed, 1 Dec 2004 15:56:02 -0800

"jim evans" <jimsnews@houston.rr.com> wrote in message
news:p5ksq09qlc01u3f9j21ra08e3kle1408nu@4ax.com
> On Thu, 2 Dec 2004 09:59:29 +1100, "Michael C"
> <mculley@NOSPAMoptushome.com.au> wrote:
>
>> "jim evans" <jimsnews@houston.rr.com> wrote in message
>> news:h8isq05uisbvc8pk1enb79h5qgvhi4i7mf@4ax.com...
>>> If so, and I upgrade to VB6 and update all users' components can I
>>> assume I don't have to worry about this problem anymore?
>>>
>>> I hope that's clear enough for you to understand.
>>
>> There is no guarentee. There is a better than average chance they
>> won't but you never know.
>
> Thanks. I think I gamble on it.

VB6 SP6 was released not too long ago and introduced several new bugs and
many developers have stayed with SP5 for that reason. SP6, however, is
appearing on various systems as users load other applications. At the very
least you are stuck with that issue assuming that no SP7 comes out to fix
the problems created by SP6. 

-- 
Reply to the group so all can participate
VB.Net... just say "No"