I can not use cookies, per company policy.???

That being said, I figured I could show animation 1 once, then set a
SharedObject. Each time after that show animation 2.

This seemed fine until it was decided that this should only happen per
session. I have since found that SharedObjects do not expire. So my thought is
this:

1. Pass an ASP sessionId in as a FlashVar. Session.SessionID
2. Use the sessionid as the value of the SharedObject.
3. If the SessionID matches the same in the SharedObject show animation 2
otherwise show animation 1 and changed the SharedObject value.

Does anyone see a problem with this approach?

Thanks,
Victor

what's the point in determining if a session has expired?

ie, why does it make a difference to you if a user

1) returns to your website after navigating away from your website (same
session)

vs.

2) returns to your website after closing their browser (different session)?

Basically my requirement says that the first time a users visits a
page show a long animation swf file, each subsequent visit to the page
during that users session show a short animation. If the user returns
then show the long animation again the 1st time, etc.

I am open to other ideas.

Thanks,
vc

Basically my requirements say show a long animation the 1st time a user visits per session then show a short animation.

Any other ideas are welcome.

Thanks,

i still don't see why it matters to the client whether 1 has occurred or 2?