🚀 go-pugleaf

We are using VB 2.0 for product development.

Yes, it is buggy. Yet the new features are needed so we are sticking
with it.


--
*********************************************************************
*   John P. Flowers            _\|/_______________________          *
*   johnf@scd.hp.com            /|\ We can tell how                 *
*   HP Santa Clara Division         far gone you are!               * 
*   Laser R&D                                                       *
*   q: What's the difference between a rabbit and software bugs?    *
*   a: Rabbits reproduce easily                                     *
*********************************************************************

johnf@scd.hp.com (John Flowers) writes:

>We are using VB 2.0 for product development.

I've noticed that too.  For example, after exiting from a compiled version of
VB/Win 2.0 that runs fine in the interpreted mode, Windows on my machine
crashed.  The standalone EXE for VB/DOS also crashed when I used the keyboard
instead of the mouse to make selections.

Has anyone else noticed other bugs with the latest release of VB?

Stacey Lum
lum@netcom.com

>We are using VB 2.0 for product development.
> 
>Yes, it is buggy. Yet the new features are needed so we are sticking
>with it.
>--

What do you mean exactly by 'buggy'.  I am waiting for VB 2.0 now.  I might
mention that I have been waiting for about 2 months and the dealers pass
the buck on to Microsoft saying I have about another month and a half to wait.
Is VB 2.0 worth waiting for?  By the time I get it, will these bugs be 
resolved?

The answers to these Questions and others await in the next episode...

+---------------------------------------------------------------------------+
|Jon Machtynger (jonm@ingres.com)                                           |
|Ingres Technology Centre. Wharfedale Rd,                                   |
|Winnersh, Wokingham. Berks UK.   (0734)-496525                             |
+---------------------------------------------------------------------------+
| Ahhh Brisbane, people actually get paid to work there... in the sun with  |
| all that fresh air and cheap petrol.... Or so ledgend has it              |
+---------------------------------------------------------------------------+

jonm@Ingres.COM (Don't Judge a book by your cover) writes:

>>We are using VB 2.0 for product development.
>> 
>>Yes, it is buggy. Yet the new features are needed so we are sticking
>>with it.
>>--

>What do you mean exactly by 'buggy'.  I am waiting for VB 2.0 now.  I might
>mention that I have been waiting for about 2 months and the dealers pass
>the buck on to Microsoft saying I have about another month and a half to wait.
>Is VB 2.0 worth waiting for?  By the time I get it, will these bugs be 
>resolved?
>The answers to these Questions and others await in the next episode...

Yes, I know what you mean.  I haven't experienced the bugs yet, but I did get
somewhat perturbed with Microsoft because they take a million years to get
registered users of their products on their database.  I had to wait for my
upgrade until they managed to get around to it: and of course that took four
or five weeks.

Sharon O'Neil
oneil@cwis.unomaha.edu

johnf@scd.hp.com (John Flowers) writes:

>We are using VB 2.0 for product development.

>Yes, it is buggy. Yet the new features are needed so we are sticking
>with it.

Buggy? Can you tell us more?

Arnd
--
   __          _
  /  )       _//                       Mail Addr. liman@cpp.do.open.de
 /--/        /                                    Am Hartweg 106
/  (_ rnd   /___ iman                             D-4600 Dortmund 1

We're using it (VB Professional 2.0) for creating prototypes calling DLLs
and such stuff.  The major thing I've noticed is how many bugs have been
fixed that existed in VB 1.0 (VB controls not working as a DDE server if the
controls were inside a frame) and the VB 1.0 Professional Toolkit (all sorts
of 3D control bugs that existed) have been fixed in 2.0.  They also made
some very intelligent additions to the language and to the user interface.
I'm very pleased with it so far.

We've also been using VB-DOS Professional Edition 1.0, and the bugs I've
found with that puppy have *not* been much fun.  This also has the worst
documentation I've ever run into with a Microsoft product, which is saying
something.

                           "The whole subject area is rife with speculation
                            and half-baked ideas, some of which are my own."

                                           -- H. Finlayson
---
                                        Moriarty, aka Jeff Meyer
INTERNET:     moriarty@tc.fluke.COM
Manual UUCP:  {uunet, uw-beaver, sun, microsoft}!fluke!moriarty
CREDO:        You gotta be Cruel to be Kind...
                 **>> Keep circulating the tapes <<**

lum@netcom.com (stacey lum) writes:

>johnf@scd.hp.com (John Flowers) writes:

>>We are using VB 2.0 for product development.

>I've noticed that too.  For example, after exiting from a compiled version of
>VB/Win 2.0 that runs fine in the interpreted mode, Windows on my machine
>crashed.  The standalone EXE for VB/DOS also crashed when I used the keyboard
>instead of the mouse to make selections.

>Has anyone else noticed other bugs with the latest release of VB?

>Stacey Lum
>lum@netcom.com

I, too have had VB create executables that crashed the system.  I don't
know the exact cause (most seemed to happen after I did some work on the
program in development mode and then created the executable).  I have
also seen problems after VB messes up the palette on the 256 color photo
I have as a backdrop on the screen.

I have found a solution that works for me -- exit windows, load windows,
start VB and load my project, then make the executable.

Robert Wallace