Re: Client/Server Applications - what to use?

I've done quite a bit client-server / GUI development over the past 7 years.
But, an ideal design keeps eluding me.  For the most part, the problems have
out weighed the cool parts.  My present interest is web browser/servlet
interactions.  It seems to me that you avoid a lot of development,
deployment, and support problems when most or all of your application is
server-based, as opposed to client-based.

If you've already decided to use VB for the client code, it seems that your
next decision is between a message based interface (APPC, Sockets, Data
Queues) and an ODBC based interface.  After all, RDO and ADO are for the
most part, merely object-oriented wrappers around ODBC.

I recommend you avoid APPC because its harder to implement than sockets and
data queues, and much less prevalent in our TCP/IP based world.

An RDO or ADO interface is the easiest to implement.   Just remember that
the underlying communication is ODBC.  The universal complaints of ODBC are
performance and reliability.  This may not apply to you if your database is
small, your users are few, and your application will never expand beyond a
local area network.

Good Luck.

<snip>
I have an application to write that I feel would benefit from a graphical,
ie VB5 front end. My question is - what is the best way to link the
application to the as/400....APPC, Data Queues, RDO/VDO, ODBC, etc, etc.
There would need to be a certain amount of validation to be performed on
various input fields, so constant communication between the two is
imperative.  Any ideas or pointers would be appreciated.
<end snip>


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