Ramzi,
Thanks for helping. I am still having problems though... Trying to just implement the simple example from that article you gave the link for: I added in the relevant bits to my web.config:
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="CustomError.aspx"/>
<pages theme="Default"/>
<compilation debug="true"/>
<globalization fileEncoding="utf-8" requestEncoding="utf-8" responseEncoding="utf-8" />
<anonymousIdentification enabled="true"/>
<trust level="Medium"/>
<profile >
<properties>
<add name="Name" allowAnonymous="true" />
<add name="Age" allowAnonymous="true" type="System.Int16"/>
</properties>
</profile>
</system.web>
then tried it out by adding in a test page with that small simple example and got this error message:
The SSE Provider did not find the database file specified
in the connection string. At the configured trust level (below High
trust level), the SSE provider can not automatically create the
database file.
What I don't understand is that is says the simple example is supposed to work wihtout a DB, and I don't want to store this info away, it's only going to be for the session really. So I am wondering whether a session variable isn't a better way of doing it and then using a global variable or something. They actually say that in the feedback responses of that post.
However, I still don't understand why that simple example doesn't work. Do I have to store the profile in DB? I mean I can see why you would want to for other stuff, but it's not what I'm after.
I would appreciate if you could point me in the right direction of maybe using a variable somehow?
Thanks again for your help!
Cheers,
Carin