At 12:43 PM 7/7/02 -0400, you wrote:
>Well normally the cookie will reside in the cookie scope so do display the
>cookie you would do
>
><@VAR cookie$theCookie>
>
>To assign the cookie to another var, which I'm not quite sure why you want
>to do that, just do:
>
><@ASSIGN NAME="theNewVar" VALUE="<@VAR cookie$theCookie>" SCOPE="local">
>
>But the there are 2 issues here:
>1- You don't need to really assign the cookie because you can access it as is
>2- Your way of determining if someone has seen the records is a bit weak
>because if someone deletes their cookies or accesses your app from another
>machine, they get to see all the records over again.
Thanks! This works just as I wanted it. I've not done much with cookies
before so I was floundering.
Yes, I agree the logic is weak. This is for a special situation and
there is no log in to the system so the only way we could show some sort of
continuity is to use cookies. Not perfect, probably not even good, but just
what the user wants. *grins*
Thanks for your help!
As Always,
Gene Wolf
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.373 / Virus Database: 208 - Release Date: 7/1/02
