Jim Lawrence
accessd at shaw.ca
Tue Jun 23 12:51:31 CDT 2009
Hi Eric: Is most of the coding being managed through the page at: https://www.roxy.com/checkout/index.jsp?process=login It sounds like you have worked around and resolved the issues that I am working with. Thanks for the information I will have to get back to you later on it. Thanks a lot. :-) Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Eric Barro Sent: Monday, June 22, 2009 10:21 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Learning .Net -- PHP Instead? Jim, You can make this "portable" by creating and encapsulating this in a user control. Once you get the plumbing in place you can instantiate this user control in any web page you want to use it in. I tend to simplify these user authentication modules and stay away from ASP.NET 2.0's authentication and membership model. I just recently completed a project for Roxy.com (http://www.roxy.com/designabikini) that incorporated these features. 1. User login is handled by a User table. 2. User registrations are handled by a Contestants table. 3. Email validation is achieved by sending the user an email link that contains a confirmation code that is essentially a GUID field. There was no need to do a time-out for validating email addresses but that would be easy to implement as well. Eric -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Monday, June 22, 2009 10:03 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Learning .Net -- PHP Instead? Shamil and Eric: I am working on standardizing logging in to a web network. The item to complete is: 1. Login interface with username, password, captcha and add if new user. 2. Adding MS SQL server for validating passwords, allow no more than 8 incorrect attempts. 3. For new users, page for getting credentials. When completed final part of validation will be to send new applicant a security coded email with a two day time-out. 4. Validate new user acceptance email back and allowing limited access. 5. A system to monitor user logins and duration and pages viewed. This interface has to be so designed as it can float anywhere on a website page and perform and monitor all the above required tasks. I would like the code to be generic and flexible enough to be easy to insert in any site with a backend... So this module will need a full set of admin accessible profiles. It is not to say that it will be for anyone but a programmer but it should make my life easier. There are of course some issues (a lot) I am having and some of my fixes seem to be generating longer lists of errors rather the fixing anything. As mentioned before I will have to put this project aside as I have recently received a paying gig in MS Access... When I get another chance and have resolved some of the basic issues I will be asking some more point questions. MTIA Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Eric Barro Sent: Monday, June 22, 2009 7:09 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Learning .Net -- PHP Instead? Jim, What exactly is not working with your ASP.NET app? Eric -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com