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

["Brad Jensen" <brad@xxxxxxxxxxx>]

----- Original Message -----
From: "Walden H. Leverich" <WaldenL@TechSoftInc.com>

> >I prefer JSP because done correctly they really fly - once the JSP is
> compiled,
>
> A valid point of JSP over ASP. ASP is reinterpreted each time. Of course
on
> a fast server, who cares. However, ASP.NET is similar to JSP is that it's
> compiled (into a DLL) on first touch. If you change the .ASPX file
(source)
> then the server will recompile the file again.
>
> -Walden

Nothing that I know of can approach the speed of compiled VB6 dlls running
in the ASP environment.

Plus you can debug in the interactive VB6 environment.

MS continues to improve the speed of ASP - even the vbscript is far faster
than it used to be.

But don't use vbscript - except to call the VB6 dll. It's loaded into memory
once as an executable, then
all invocatios have their own address space. Since the sessions can have
timeouts, the VB6 dll can maintain
state between web pages. You write the program like a Windows program, but
use the request, response, and system objects. Extremely fast development,
fast programs, high capacity. We did one program
that supported 1000 simultaneous web logons - in 64MB on NT 4 on an Intel
Pentium 100 mhz (not 1000, 100).

Also, while ODBC and OLE/DB can be used for talking to the AS/400 in Client
Access, my impression is
that IBM has in recent releases significantly sped up the OLE/DB version.

By the way, we have noticed that CA has cratered OLE/DB for disconnected
recordsets in CA on XP, we had
to go to XML.

Brad Jensen
www.elstore.com
The best Report Archiving, Imaging, Signature Capture
and Report bursting with email and web delivery for
IBM Midrange - since 1989