🚀 go-pugleaf

In article <C0pqr1.BGJ@ccu.umanitoba.ca> umlamott@ccu.umanitoba.ca writes:
>All of the replies dealt with poor experience with this product; has
>anyone out there had a GOOD PowerBuilder experience? And if not, which
>development tool do you use instead?

We have chosen powerbuilder as our current windows application programming
language.  We chose the product because of its ability to connect to SQL
server.  At the time, Visual Basic didn't have any SQL links.  We has problems
with support from Gupta which was the only other development package that 
supported SQL.  PB is fairly powerful...it gets the job done.  The main
flaw we've come across is its report writing capabilities.  The speed of
the product is directly related to our SQL server - people in my group
have developed usable programs with PB.

However, I was slated for a PB class...until we received Access.  I'm just
starting 2 project and I am using Access(to better evaluate the program).
Access appears to have as much functionality - for us - than PB.  Less
or no coding from Access to get a prototype database.  Again, I think
our speed is relative to the SQL server, but Access matches PB in data
access times.
Once you get to complicated things, programming is probably very similar
between products.

The complicated part is this...Powerbuilder HAS a run time...that is,
you can make stand alone apps.  The PB license is kinda expensive, but
you can put your app anywhere(I think) at no extra charge.  Access
does NOT have a run time yet.  The slated release (I've heard) was Summer
1993.  Assuming there is no run time...by a bunch @ $99 so everyone can
get to my db...or wait & find out the run time is expensive...or have
NO run time, buy everyone access software @ $375 a pop.

i   Reed Keel     -  mail:rkeel@fnugget.intel.com  -  The i's have it   i
i-Everything is my opinion, otherwise someone else would've said it     i
iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii