abcb <> abcab

[George Hester]

So what's this? a is a ASP page. Clicking on a link there goes to the b ASP page. Clicking a link on that goes to the c ASP page. The idea here is to keep the visited attribute throughout the process. So if I go a->b-.c>->b using links dynamically generated the visited attribute holds up on the b page. Even later a->b. But if I go a->b->c->a->b the visted attribute does NOT hold up on the b page. Is there something I can do with session so that if the session is made in the c page then I can make sure the visited link in the b page holds the visited atribute? In other words abcb = abcab. Thanks.

--
George Hester
_______________ _______________ ____

[Aaron [SQL Server MVP]]

Re: abcb &lt;&gt; abcab

George, I have absolutely no idea what you're talking about. Are you
speaking of the VLINK attribute of the body tag? What does it have to do
with ASP?

--

http://www.aspfaq.com/

(Reverse address to reply.)





"George Hester" <hesterloli@hot mail.com> wrote in message
news:%23lEgbkbc EHA.716@TK2MSFT NGP11.phx.gbl.. .
So what's this? a is a ASP page. Clicking on a link there goes to the b ASP
page. Clicking a link on that goes to the c ASP page. The idea here is to
keep the visited attribute throughout the process. So if I go a->b-.c>->b
using links dynamically generated the visited attribute holds up on the b
page. Even later a->b. But if I go a->b->c->a->b the visted attribute does
NOT hold up on the b page. Is there something I can do with session so that
if the session is made in the c page then I can make sure the visited link
in the b page holds the visited atribute? In other words abcb = abcab.
Thanks.

--
George Hester
_______________ _______________ ____

[Bob Lehmann]

Re: abcb &lt;&gt; abcab

It's probably in a *.asp page.

Which reminds me, I have an ASP site about fused glass. Where can my client
get the best prices on Bullseye glass? I need to do a site on auto mechanics
pretty soon too. My truck hasn't been running well lately.

Bob Lehmann

"Aaron [SQL Server MVP]" <ten.xoc@dnartr eb.noraa> wrote in message
news:%23jSUIcec EHA.1356@TK2MSF TNGP09.phx.gbl. ..[color=blue]
> George, I have absolutely no idea what you're talking about. Are you
> speaking of the VLINK attribute of the body tag? What does it have to do
> with ASP?
>
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
>
>
>
> "George Hester" <hesterloli@hot mail.com> wrote in message
> news:%23lEgbkbc EHA.716@TK2MSFT NGP11.phx.gbl.. .
> So what's this? a is a ASP page. Clicking on a link there goes to the b[/color]
ASP[color=blue]
> page. Clicking a link on that goes to the c ASP page. The idea here is[/color]
to[color=blue]
> keep the visited attribute throughout the process. So if I go a->b-.c>->b
> using links dynamically generated the visited attribute holds up on the b
> page. Even later a->b. But if I go a->b->c->a->b the visted attribute[/color]
does[color=blue]
> NOT hold up on the b page. Is there something I can do with session so[/color]
that[color=blue]
> if the session is made in the c page then I can make sure the visited link
> in the b page holds the visited atribute? In other words abcb = abcab.
> Thanks.
>
> --
> George Hester
> _______________ _______________ ____
>
>[/color]

[Zeke]

Re: abcb &lt;&gt; abcab

George,
Your code needs to be flexible, so that the code in c checks for
current values before initializing your session variables. I beleive
that session variables won't error out if you check them for
existence.

As In:
If ISNULL(Session( "visitedB") ) Then
Session("visite dB")=False
End If

There are a variety of other ways to get this done as well.


If you are just talking about vlink='#color' tags not working, it
could because your site or your machine is caching the page. I use the
full cache blocking code in most ASP pages myself:

<%@ Language=VBScri pt %>
<%
Option explicit
Response.Buffer =true
Response.CacheC ontrol = "Private"
Response.Expire s=-1
%>

Place it at the start of the main ASP document for full effect. To
help guard against caching. It helps, but it won't handle all cases.





"Bob Lehmann" <nospam@dontbot herme.zzz> wrote in message news:<ei1W3aicE HA.1408@TK2MSFT NGP12.phx.gbl>. ..[color=blue]
> It's probably in a *.asp page.
>
> Which reminds me, I have an ASP site about fused glass. Where can my client
> get the best prices on Bullseye glass? I need to do a site on auto mechanics
> pretty soon too. My truck hasn't been running well lately.
>
> Bob Lehmann
>
> "Aaron [SQL Server MVP]" <ten.xoc@dnartr eb.noraa> wrote in message
> news:%23jSUIcec EHA.1356@TK2MSF TNGP09.phx.gbl. ..[color=green]
> > George, I have absolutely no idea what you're talking about. Are you
> > speaking of the VLINK attribute of the body tag? What does it have to do
> > with ASP?
> >
> > --
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
> >
> >
> >
> > "George Hester" <hesterloli@hot mail.com> wrote in message
> > news:%23lEgbkbc EHA.716@TK2MSFT NGP11.phx.gbl.. .
> > So what's this? a is a ASP page. Clicking on a link there goes to the b[/color]
> ASP[color=green]
> > page. Clicking a link on that goes to the c ASP page. The idea here is[/color]
> to[color=green]
> > keep the visited attribute throughout the process. So if I go a->b-.c>->b
> > using links dynamically generated the visited attribute holds up on the b
> > page. Even later a->b. But if I go a->b->c->a->b the visted attribute[/color]
> does[color=green]
> > NOT hold up on the b page. Is there something I can do with session so[/color]
> that[color=green]
> > if the session is made in the c page then I can make sure the visited link
> > in the b page holds the visited atribute? In other words abcb = abcab.
> > Thanks.
> >
> > --
> > George Hester
> > _______________ _______________ ____
> >
> >[/color][/color]

[George Hester]

Re: abcb &lt;&gt; abcab

Alright now I figured out what was happening. It turns out that:

http://www.myserver.com/page.asp is different then

http://www.myserver.com/page.asp?hi=hello

Since navigating around my site uses many of these parameters, I didn't
realize that visited depends on the parameters used. Not their values but
that they exist in the addressing.

So all I did was make sure that returned to pages included the parameters
that they were originally accessed with. Again not their values. For
example if I returned to page.asp above I could do it like this:

http://www.myserver.com/page.asp?hi=

and the visited would show correctly. I used the FSO to make sure that
pages accessed from out of the site would get their correct parameters.
Thanks to all who responded.

--
George Hester
_______________ _______________ ____
"George Hester" <hesterloli@hot mail.com> wrote in message
news:#lEgbkbcEH A.716@TK2MSFTNG P11.phx.gbl...
So what's this? a is a ASP page. Clicking on a link there goes to the b ASP
page. Clicking a link on that goes to the c ASP page. The idea here is to
keep the visited attribute throughout the process. So if I go a->b-.c>->b
using links dynamically generated the visited attribute holds up on the b
page. Even later a->b. But if I go a->b->c->a->b the visted attribute does
NOT hold up on the b page. Is there something I can do with session so that
if the session is made in the c page then I can make sure the visited link
in the b page holds the visited atribute? In other words abcb = abcab.
Thanks.

--
George Hester
_______________ _______________ ____