If the user have to create an account so that he could come at later time to
consult the status order, do new commands more easily or anything else, when
the user register himself in the database, you have to identify them. You
could use :
- an autoincrement number
- a GUID, basically a big random unique number that is created using
System.Guid.NewGUID
The key point was that the SessionID identifies just a particular session.
That is if the same user returns on your site at a later time, he'll have a
brand new session id i.e. it is not sufficient to identify the user.
Patrice
"Amir Ghezelbash" <am*******@hotmail.com> a écrit dans le message de
news:%2****************@TK2MSFTNGP11.phx.gbl...
Hi Thanks for your responses, could you elaborate on what you man with
GUID , yes i do want to assing every USER an uinque ID so i can track
their order
---
Best Regards
Amir
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!