> >
> > You could do that, but it would not be very secure. The user knows that the password is based on the date and the user knows the algorythm (or he/she wouldn't be able to log on.) Now that user gets fired. Your password algorythm is hard coded and is therefore VERY difficult to change. You basically need to recompile if you wish to change your password algorythm. That employee who was fired decides he wants revenge so he gains access to one of the network computer logs into your app before you can recompile and he does as much damage as he can.
> >
> > Compare that to using Windows security. The employee is fired, SysAdmin deletes that user's account and the user cannot even log onto the network - let alone onto your app.
> >
> > Ken
> > You shall know the truth - and the truth shall set you free. (John 8:33)
> Sir,
> Thats true. We can eliminate that particular User from our own database too. Thats why I said - There is no boundary for imagination.
> With Regards,
> Biju Thomas

But now, you need to eliminate the user from both Active Directory AND your user table - why do it twice?

Ken
You shall know the truth - and the truth shall set you free. (John 8:33)