RE: Client/Server Applications - what to use?

Hey, be nice <G>. 

Actually, VB apps to get implements and work quite well. The general rule of
thumb we've come up with over the years is to start with a VB app (or COM
object in the case of the web) and then only if performance is REALLY bad
replace certain parts of the app with C++ COM objects. More often than not
we don't go to C++. The exception tends to be where we want to store objects
in the Session and Application space in ASP, can't do that with VB -- well,
you can, but you don't want to.

-Walden

-----Original Message-----
From: nina jones [mailto:ddi@datadesigninc.com]
Sent: Wednesday, August 30, 2000 10:24 PM
To: MIDRANGE-L@midrange.com
Subject: Re: Client/Server Applications - what to use?


> 
> There seems to be a lot of people using Visual Basic, but  do Visual Basic
> applications ever get finished and installed, or are they just
> works-in-process forever?
> 

there was a fellow in the web class that was a visual basic user, and
asna has a way to also use visual basic, but i haven't found it
necessary to go there yet...

nj
+---
| 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 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
+---