OK. Well, somewhere we need to declare a Session Variable. This is easiest because it will automatically persist from page to page without you having to do it through code. In this case, we are going to do it on the second page and you may need to repeat this on other pages that are accessed from the first page depending on your need.
Now, on the 2nd page, you'll initialize the variable like this. Put this before any HTML tags.
<%
IF Session("user_status"

= "" THEN
Session("user_status"

= "0"
END IF
%>
The IF.. ENDIF is designed so that it won't initialize the user_status variable if one is already present for this visitor. You mentioned that people may be accessing these pages several times. This will take care of that. If the Session("user_status"

has already been created, this code will be ignored.
Now, anywhere throughout the application, you can examine that Session Variable like this.
<%
IF Session("user_status"

= "" THEN
' do something
END IF
IF Session("user_status"

= "0" THEN
' this visitor HAS been to your second page
END IF
%>
You can change that variable at any time like this.
<%
Session("user_type"

= "1"
%>
Remember, I would always examine the session variable before initializing it or changing it using IF .. ENDIF statements like I have provided above.
Session variables are great because they persist automatically in IIS memory for each user. No need to pass them as form elements from page to page. And you can have as many Session variables per user as you wish.
You might have Session("user_type"

and Session("shop_cart_count"

and so on and so forth with each variable being unique to each user. This is standard operating procedure for most applications with shopping carts, etc... because the variables are kept on the server and are not visible by the visitor through any source code or anything like that.
There's a little more to it so if you get stuck, don't hesitate to let me know.
TW