I agree with Tomalak - I'm really not sure why you (or need) to include the same file twice (?)
This seems to be a bad design philosophy, it might be better to encapsulate the subroutines in the include file as functions or subroutines that you can name — no need to include it twice.
Also, while you cannot calm down, you can refuse, but I do not want to encourage bad practices, given what you seem to want to do.
Instead, you can use something like this:
Include.asp:
<% Function SetCookie(scVar, scVal) Response.cookie (scVar) = scVal End Function %>
Asp page:
<% Dim A A=1 SetCookie "Beer", A A=1 ' This is kind of redundant in this code. SetCookie "Beer", A %>
However, if you want to use global variables and are saved with inclusion twice, you can do it this way by adding another include for global variables.
Globals.asp:
<% Dim globalVarA ...other global stuff here.... %>
Include.asp:
<% globalVarA=1 Response.Cookie("beer")=globalVarA %>
Now the asp page:
<% Dim A A=....something...... %>
source share