🚀 go-pugleaf

Well, since people are expressing opinions about VB/DOS, I'll throw in my
$0.02 worth.

Firstly, I bought the professional edition upgrade for $199 which contains
the whole 9 yards. Overlay support, ISAM support, etc.. I am using a 
286-16 w/ a math chip & 2.5 Megs of RAM. 40 meg IDE harddrive.

I must admit I was pretty suprised when I installed the software onto my
system and found it needed ~11 Meg!! (my harddrive needed some house cleaning
anyways :).

I am in the midst of coverting several modules of a large appplication into
VB/DOS from QB4.5.  Each module was about 4000 lines in QB4.5 & I have about
4 or 5 modules. So far I have found VB extremely easy to use with excellent
on line help and _MUCH_ improved documentation over QB45. The folks at MS
finally ditched the idea of putting a users guide and a ref. manual in the
same package. This makes it much easier to find stuff regaurding syntax etc.
without having to wade through the entire users manual. 

As using VB is my first experience in using any type of object oriented 
programming, the basic idea took a little getting used to but again, the 
VB environment makes it simple for the novice to setup efficient event 
procedures for forms. Much of the "innerworkings" routines of my QB45 programs
(ie data handling, file procedures etc.) was directly copied into my new 
VB programs and are working with no problems.

Creating and editing forms is once again quite simple as the form editor
is also quite user friendly. Again, good online help is one keystroke away:).
It's so nice to be able to create a good looking user interface in a few
minutes instead of struggling using LOCATE & COLOR statements all over the 
place. 

I really appreciate the extra programs included with VB. These programs
contain dialog boxes which virtually every program uses and which can be
used in any other programs by either adding them to the .MAK file (like
you could ibn QB45) or by bunching several together and using them as a
library (like I did). Both methods work flawlessly and save writing code
for such things like an open file dialog box, a save file dialog box, a 
desktop setup dialog box, etc...

All in all, VB is exaclty what I was looking for. A good efficient object
oriented language which I didn't have to completely scrap my QB code, but
the user interface is 1000% better looking then it used to be.
 



-- 
******************************************************************************
	Peter G. Millard  *  INTERNET: v057n5um@ubvms.cc.buffalo.edu           
 	SUNY @ Buffalo    *          : millard@acsu.buffalo.edu
*****************************************************************************