That's DW .net code (note the MM_) so I really have no idea
what it's doing
specifically.
You could always put code on the default.aspx page, check
credentials, and
then redirect as necessary.
FYI, ASP.net is a dead technology for DW. If you want to get
into ASP.net,
you're going to want to switch over to VisualStudio for your
coding.
-Darrel
> I've set up a web application that uses a standard Form
to submit a
> username
> and password and validate against what's stored in a
table in my db. Once
> I
> figure out how to implement role-level security
(separate post), I'd like
> to
> specify the landing page that the users are taken to.
The technique I'm
> using
> takes a person from login.aspx to default.aspx after a
successful login.
> I
> don't see what is controlling this and how I could make
it something other
> than
> default.aspx for anyone let alone based on some
condition.
>
> I'm using DW CS3 on an XP machine. I'm wondering if this
is controlled by
> the
> infamous DreamweaverCtrls.dll
>
> Any suggestions? Login code is below.
>
> <%
> if dsLogin.RecordCount > 0 then
> Session("MM_Username") = Request.Form("tfUserName")
>
FormsAuthentication.RedirectFromLoginPage("tfUserName.value",
false)
> else if ((Request.Form("tfUsernName"))) <> Nothing
_
> OR ((Request.Form("tfPassword"))) <> Nothing
> response.Write("Sorry. We weren't able to sign you in.
Please try
> again.")
> end if
> %>
>