[AccessD] OT: FrontPage Websites

I've never had a reason to go to ASP.Net.  I've seen it, played with it
briefly, got bored, and went back to my asp/VB combo.  I know it looks
great, but ASP.Net uses a LOT of overhead that just gives me the
willies.  On a modern machine, it isn't noticeable, but I always strive
to stay as lean and mean as possible.

I have a questiona bout VS WD Express though....you say it is 'easy to
use'  Are we talking about easy for a developer, or easy for a user?  I
ask, because I don't really use FrontPage.  I utilize the navigation,
but I just write the HTML in MS Script Editor.  But we use FP on our
site, because we have people that update the content that are no where
near 'web developers', and the fact that FP is pretty much a web working
version of Word, makes it easy for them to do what they do.  But if this
WD Express is easier the FP for a user, I may have to look into it.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William
Hindman
Sent: Friday, December 14, 2007 2:15 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] OT: FrontPage Websites

...sigh ...shakes head ...Asp and Front Page are dead ...long replaced
by 
Asp.Net and Visual Studio Web Designer Express Version 8, both of which
are 
free, easier to use, and incredibly more capable.

William

----- Original Message ----- 
From: "Drew Wutka" <DWUTKA at marlow.com>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Friday, December 14, 2007 1:00 PM
Subject: Re: [AccessD] OT: FrontPage Websites


> Ok, here's the first of the two classes in my SiteNav2006.dll.  There
is
> also a module, for my DBConnect function, which just sets the
> ADODB.Connection argument to a new ADODB.Connection, set's it's
provider
> to Jet 4.0, then sets the extended proprerty for the workgroup file
and
> opens the secured database.
>