Re: access as/400 database files w/Visual Basic 6

["Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx>]

PHP.

Very easy to learn.  If you run it on Windows, you can interface COM.
Running on UNIX you can interface its local libraries.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
To: <midrange-l@midrange.com>
Sent: Friday, August 09, 2002 6:16 PM
Subject: RE: access as/400 database files w/Visual Basic 6


> > From: Walden H. Leverich
> I think the war has cooled down over the last year or so, Walden.  ASP is
> easy to use.  It's MS specific, but these days that's not a huge issue.
> It's just one you have to be aware of.  I prefer JSP because done
correctly
> they really fly - once the JSP is compiled, it's basically sitting in
memory
> and spinning out data.  Of course, you can mung it up with a bunch of
junk,
> but you can do that with ASP too.
>
> JSP, however, requires at least a little Java knowledge and a servlet
> engine.  And the loading of the data is (usually) on the host.  I forget
how
> exactly ASP s traslated - it's all in the browser isn't it?  If so, that
> means a lot of load on the client, but personally I kind of like the idea
of
> making the client do the work.  Then again, a properly designed JSP
> implementation can have the web server on a separate box than the business
> logic.  I have one client using Tomcat on FreeBSD calling redeployed RPG
> programs on their AS/400.  The 400 is now entirely batch, with no
WebSphere
> overhead.
>
> In any event, I think the deployment language is a matter of personal
> preference.  As long as the architecture separates the UI portion of the
> deployment from the business logic (be it through stored procedures,
sockets
> or data queues) then I'm happy.
>
> Joe