🚀 go-pugleaf

Well, it did occur to me later that I was being harsh in my criticism
of microsoft for the introduction of these basic products.
After all, this partly in response to demands of users with
many different needs.  But trying to figure out where to go next from
QB 4.5 is rather frustrating.  The fact is, most people I know who
want a graphical environment run windows on their machines.  So, what
do I do if I want a Basic that will compile number-crunching programs
written in QB 4.5 and yet will provide the user-interface of
Windows?  Does Visual Basic for Windows provide this? Is it
also compatible with BASIC PDS?
   Secondly, I confess to ignorance of when BASIC PDS was released.
My grievance was mainly concerned with what I perceive to be 
minimal improvements in my programs when altered and compiled
in professional basic a couple of months ago.  It does have some
nice features, particularly for database applications, which I
have not used.  I have used QB 4.5 for quite some time and do
feel that it was an excellent BASIC.
   Lastly, if Visual Basic for DOS is intended to be for the
purpose of generating code that will later be used in VB for
windows, does this mean that VB for windows will support
all the other commands that are available in QB and PDS
(excluding those that constitute "mucking with the system")?
It seems to me that this is a necessary requirement for a
language designed to create applications that are
"portable to and from windows".

I can't be the only user of QB 4.5 who feels this way
because I've seen numerous articles asking about where to
upgrade from QB 4.5.  It is possible that I should have
investigated VB for Windows more carefully, but for the
kind of programs I run, a fairly high level of
compatibilty with QB 4.5 is needed.  If I'm completely
ignorant, please enlighten me.


Ted Carver                ted@rice.edu
i