It's not impossible. And, I don't think you understand what is going on
there.
This is what happens when a site chooses not to rely on cookies or sessions
for tracking users....
1. User enters site
2. A unique ID is assigned to the user, usually from a DB generated unique
ID
3. The unique id is stored in a DB
4. The unique ID is appended to *all* URLs to track the user, and passed
from page to page in the URL
5. If the unique ID is needed on a page, it is looked up in the DB and used
as a key in the DB for whatever transaction took place
You are making this cookies / no cookies problem way more difficult than it
needs to be.
You need to come up with some Use / Business Cases to determine if the no
cookie problem is really a problem to begin with. If no cookies will
severely impact your application, then code a solution that doesn't rely on
cookies. Don't add complexity developing 2 solutions to the problem
If there is bearable risk in not supporting the no-cookie folks, then direct
them to page that informs that accepting cookies are required, and let them
decide.
I'm not trying to be critical - You are obviously working very hard to do
whatever it is you are doing. But, you are lacking some fundamentals that
are causing you to go down paths trying to finding solutions to problems
that don't exist.
I suggest reading some basic literature on server-side programming and ASP.
Also, read this...
http://www.aspfaq.com/show.asp?id=2054
Bob Lehmann