It is already like this. Unwanted controls have a tab index -1. Controls are in order. But the problem is it goes to the address bar... I want to fully utilize every thing.

I don't think the back button can be disabled but I think we can fake the functionality using javascript. What I think you can do is, you can make sure a newly selected page replaces the previous one in the page history list try to use something like this in javascript location.replace('mynewPage.htm'); The location.replace('whateverUrl.aspx') call will replace the current page in the history list with the new page thus preventing going back to the current page. You might also use that in a link with new page otherwise you will have to open that page without a toolbar or menubar Hope this gives you a a starting point

I would ensure the applications were tested on XP. The test strategy should endevour to test all code paths. Ideally unit testing should be performed and compared against know good results. 2) Issues, I have had problems with the vanilla XP. You may want to specify at least SP1 as the base OS. 3) Are you going to migrate your development environment to XP? If so why would you not set up a test system to ensure things are running smoothly. 4) No data conversion issues to be worried about. Ant. I'm hard, yet soft. I'm coloured, yet clear. I'm fruity and sweet. I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)