• Subject: Re: Access & Scaling
  • From: DAsmussen@xxxxxxx
  • Date: Fri, 15 Jan 1999 07:50:14 EST


In a message dated 99-01-14 23:38:02 EST, you write:

> You are comparing apples and oranges here. While you say that the VB program
>  was stripped of its SQL it was also stripped of its "data widgets." Data
>  widgets (aka bound controls) are really cool from a prototyping point of
>  view, but I've found them to be an absolute pig at a production level. More
>  direct data access may have saved your VB app. Also, why was the VB app
>  going to SQL server to then go to Oracle, seems like it was jumping through
>  hoops to get the data.

I don't pretend to know how it worked, all I know is what the developer told
me.  AFAIK, all the data widgets were used for was to produce a "data grid"
similar to a subfile on the forms.  The app was still in VB, just running on
the AS/400.  I further don't pretend to know why SQL server was used, other
than that was what the network folks _told_ the developer to use.  Ironically,
once the app was ported to the /400 and started running at a decent speed, a
new manager took over planning and decided he didn't want to use it >8(...


Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"I'm going to tell my 9 children by eight different women that I played
against the great Michael Jordan" -- Shaquille O'Neal
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].