I t all depends on what information the user is trying to access. If it is just a normal site I see no reason for not saving the login as a cookie. but you will need to have an option to turn the cookie login off, as the user might not be using the same computer.
If the user won't delete the cookie!<BR><BR>I usuall keep an id for the cookie, plus the value of the cookie, in a database.<BR><BR>If he delete's the cookie, you can try to do different checks with the id.
Well its a administration part of the site but its checks the database and see if the have access to it but they also can use the cookie to log into forums and chat and **** what do you think i should use? I could use both couldnt i?
On my last site I used cookies and a login page. If the cookie is present the user is taken straight into the site, otherwise they have to login - the login page checks the details against those stored in an xml document (fetched using the login details to make up the document name!)