Syed Abdul Khader wrote: This is not the problem due to server resources. Well in the following scenario sessions can be dropped due to server resources: - the server is IIS 6 (windows 2003) - his application runs in an application pool where a maximum memory usage is defined - his app has a memory leak In this situation, his app is using more and more memory, untill it hits the maximum defined in IIS. The app will then restart, and all sessions will be lost. Gidon

This is a documented bug in the framework: VB.NET: http://support.microsoft.com/kb/309482[^] C#: http://support.microsoft.com/kb/311754[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Note that this function is not very efficient. Why is b1 an integer to begin with? And as for reading a single byte at a time... my blog

LeeOvEngland wrote: I want to be able to keep the object live so I can use it on this page or any other page I may navigate to. I have used Session to store the objects and this seems to work but it involves checking for an instance of the object in Session on Page_Load() event and I understand that it is not the correct way to do this. Why not? unless they are bloody enormous this is a perfectly resonable thing to do. Create a wrapper class for your session state to encapsulate the Session["easytomistypename"] stuff and code away. Ryan

Thankyou Marcie

Why not use the code behind file to remove the cluster and make your aspx page more readable?