FYI, here's a quote from Woody's Office Watch (WOW) that blasts Microsoft for releasing VB6 with major bugs. If you think we have problems with VFP6, they're nothing compared to VB6 problems.

Best Regards,
jmu

=======================BEGIN QUOTE===========================

--==>> WOW -- WOODY's OFFICE WATCH <<==--
(your own Microsoft Word & Office guru every week!)
14 October 1998 Vol 3 No 44

http://www.wopr.com/wow/

DON'T INSTALL VISUAL BASIC 6 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you have a copy of Visual Basic 6, don't install it. If
you don't have a copy of VB 6, don't buy it. And - please!
- if you have a new application developed in VB 6, don't
distribute it.

If it sounds like I'm backtracking on my glowing review of
VB 6 in the September 1998 issue of PC Computing - and all
the nice things I said about VB 6 in previous editions of
WOW - I am. Why? VB 6, which was just released a couple of
weeks ago, has bugs all over the place. So much so that
Microsoft is already promising a Service Pack (read: bug
fix) - and warning developers not to release any software
they've produced with VB 6.

...

Mike Craven created a great little utility called Window
Switcher, written in Visual Basic for Applications and VB
5. We're showing it in the November issue of PC Computing;
I'll tell you about it next week. It uses a VBA/Excel
project to launch an application written in VB 5, which in
turn uses Automation to link back to Excel. The utility
works like a champ. Then Mike installed VB 6 and boom! A
simple VBA/Excel command suddenly stopped working. The
whole utility gave up. And there's nothing - not even
uninstalling VB 6 and re-installing VB 5 - that will make
it work again.

It isn't just us and our utility. There's VB 6 fallout all
over the place. For example, ever since installing VB 6, we
can no longer access the properties dialog for a form field
by double-clicking on it. Word 97 goes down every time with
a GPF. What gives, Redmond? Which files does the VB 6
installer clobber?

The moral of this story: until Microsoft releases Visual
Basic 6 Service Pack 1, supposedly later this month, stay
away from VB 6. See http://msdn.microsoft.com/vstudio/sp/
for the official story. Man, I sure hope somebody on the VB
team is looking hard at the VBA and Office fall-out.

Hey, SteveB! Are you reading this? You're concerned about
bugs in Win98? HA! Win98's a cake walk compared to VB 6.
And I wonder how many third party VBA licensees will get
caught in the VB 6 trap... If I were Visio or AutoCAD or
Corel and paid good money to license VBA, only to have the
VB 6 upgrade break it, I'd be all over your butt.

Hey, BillG! Get the %$#@! packages off store shelves, NOW,
okay? Whoever made the decision to continue shipping VB 6
in this condition - and, of all things, *slipstream* VB6
SP1 - should be strung up by their pea-sized brain. You
want stupid? This is stupid!

It's a sad day, indeed. I can remember when VB had an
enviable reputation as one of the most reliable products MS
ever released. Slowly that reputation has been eroding, and
with VB 6 it's been thrown, screaming, out the window. The
ludicrous slipstream cover-up makes its demise all the more
pitiful.
=====================END QUOTE================================