[AccessD] Web Applications

Therein lies the problem with the recommendation to go with classic ASP
versus ASP.NET...

You mentioned that you compile your code into a DLL. Now, how would a
beginner know to do that using VB6...much less know what to put in those VB6
modules and *then* know enough to instantiate the object you just created
using VB Script on their classic ASP pages?

Not to mention the fact that when you deploy your DLL to the server you will
have to make sure that it's registered.

Fortunately with ASP.NET you don't have to worry about all those things
because it's a framework and the framework does all the heavy lifting for
you. Am I right or am I right? :) 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Monday, April 06, 2009 8:47 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Web Applications



<snip>
  I do have my core code 'compiled' as a .dll too. Plus with what I do, I
use either .asp or .htm extensions, it's just a matter of tweaking the ISAPI
filters to read .asp code in whatever extensions you want.

<snip>
 I handle everything in my .dll.  Most of the
time I am recording the data then and there, though to pass information to
another page there is always a session variable to hold the info.  No big
deal.


>>> Again, using a VB .dll.  It can be ported to any web app or for that
matter, any system that can use an ActiveX .dll.