Grapes-R-Fun wrote: ...and no matter where I stick FormsAuthentication.SignOut() it doesn't kill that darn cookie! Am I missing something? First two obvious questions are: 1) Is the code executing? The function can't work if it is never being called. 2) Have you followed all the directions of the documentation for the SignOut method?

I think it may be here on your installation DVD: x64\Setup\sql_ssms.msi this is setup of SqlServer Management Studio Human knowledge belongs to the world

Problem was fixed by 3 wonderful gentlemen!! Apparently the temp files were accumulating since Nov 07. :-D Green Grape

Thanks alot George!! Grapes

Thanks a bunch Mark!! I really like your signature, btw - it's so witty :-) Nila

It's not about making myself comfortable; Im just trying to remedy this and move on- there is lots of pressure when you develop for an emergency operations type group. And I agree with you on finding out exactly WHY sometimes things behave the way they do :-) But now is not the time for that, maybe later. Let me do a couple of things, and then I will send you the code. Thanks again! Nila

i hear ya... remember debugging for hours just to find out you are missing that d*mn semicolon?!? ;P Nila "...for that, I will need a large cup of coffee and a bran muffin!" -Samantha Bea

Thanks Guffa, it worked like a charm!!! :-D Nila

I took your advise and looked around; after putting together parts of other people's solutions I finally was able to get it right. Turns out I had to provide yet another callbackEventReference (with a function named Release(arg, context)) that would tell my server to do something, and I called that function from within the timer function... long story short, it worked and Im super happy :-D Nila Fridley

Hi Colin, I agree with you in that just because a developer knows how to look-up msdn2 and encrypt his/her code doesn't mean that he/she is a good developer. In my original posting what I meant to say was: (I am trying to be a good developer) && (encrypt as much info as I can). Unfortunately we don't automatically think in that logic ;) Nila

Placing the html tag in the Content control does not make sense to me. Here are a couple of options: + Just ignore the error if it's working. + Turn off the validation in the VS options settings (Tools|Options|Text Editor|Html|Validation|Show Errors). + Instead of placing the base tag in the content control, you can put the Literal control in there, and assign the base tag via the Text property of the Literal control in code.