If anyone out there who is a 'thePhile' expert has any advice
on this I would--so would DoonBug--really appreciate hearing your
thoughts. Can anyone suggest a possible problem with the way the
app is set up vis-a-vis sql server, or the database itself.
I have checked and re-checked SitePrincipal.
vb, SiteIdentity.
vb,
web.config, global.asax.
vb, user.
vb in both accounts.data and
accounts.business, accounts.config, login.aspx.
vb and all others
I think might affect the authentication. No difference in my code
and the original 'thePhile' site.
The ONE THING I have done differently is change "FirstName" and
"LastName" in the accounts constructors and methods to other
names for my use...but I have been very careful to make those
changes in all needed places like the datatable, storedprocs, and
all methods and constructors and properties.
I'm at a loss now for where to look. If 'new.aspx' will create a user
and put it's info in the datatable and redirect to 'default-
.aspx' and show the correct personalization info in the header
control; but then login.aspx won't accomplish the authentication,
can anyone think of what file in the site or what in the database
might cause this to happen?
Thx. much,
R Corcoran, Jr.