🚀 go-pugleaf

In article <1992Dec20.171741.29641@eng.umd.edu>
equine@eng.umd.edu (Melinda L. Gierisch) writes:
 
>
>
>For the last 8 months my group has been developing a Windows
>application using the BC++ 3.1 Object Windows Library.  This
>program accesses Paradox tables using the Paradox Engine.  Someone in
>the group suggested using Visual Basic for much of the user interface
>because he believes it is more flexible and easier to use than OWL.
>No one else in the group has any experience with Visual Basic.  My
>questions are:
>
>1)  What is the "ramp up time" or learning curve for creating windows,
>dialogs, etc. with Visual Basic?  We needed about 3 months to get
>fully comfortable with OWL.
>
>2)  How easy / difficult would it be to combine Visual Basic windows
>and dialogs with BC++ functions for database access (these have
>already been written and are not OWL dependent)?
>
>If anyone out there has experience programming in both Visual Basic
>and C++ I would appreciate any help.
>
>Thanks in advance,
>Melinda Gierisch
 
The only thing I can respond to in this article is the question pertaining to
learning curve on Visual Basic.  When it comes to designing the interface
and creating the dialog box - one full day would get anyone remotely familiar
with programming up to speed.  I've written in C for DOS and Visual Basic is
hundreds of times easier with user interface.  I can't offer any advice on
ease of importing C++ code, or doing database work, but as for ease of design
and interface, I don't think VB can be beat.
                                     -Brad Porter
DRPORTER@SUVM