Hi Rastgar Many thanks for the pointer - FYI my implementation of the initialisation, is like this: (c#) StringBuilder sb = new StringBuilder(); sb.Append(""); sb.Append("var szValue = document.getElementById('Panel1');"); sb.Append("szValue.scrollTop = 146;"); sb.Append("szValue.scrollLeft = 182;"); sb.Append(""); ClientScript.RegisterStartupScript(typeof(string), "Init", sb.ToString()); This then just runs at startup. And of course I can harvest the values from the user by any number of means Once again, many thanks regards, John

Nila I got an email, but can't see your post. As I'm online, I thought I'd respond straight away. I have the full version of VS2005 and I don't believe I set this project as a template - although I might have done unwittingly. I actually don't know how I would do that yet! (I'm very experience at VC++ in version 6 only and am crash-coursing in ASP.NET & C#!!) I just loaded the project, watched the video and moved on. thanks again

You're welcome. I believe I remember reading that the wizards in VS2005 changed from a default of building ANSI applications to UNICODE. Believe it or not, there are advantages to building apps as UNICODE. They are much easier to translate to other languages (which may not be a concern for you). They also have something of a performance advantage. Windows itself uses UNICODE. With ANSI applications, there is an implicit conversion from ANSI strings to UNICODE with strings you pass to Windows, and the reverse when Windows returns strings to you. Software Zen: delete this; Fold With Us![^]