Low rate of answer

It does not seem to be the best place to be answered.
Any suggestions?

Well, I'm going to guess that you asked a question that didn't get an
answer. There are several reasons this might happen. Here are some of them:

1. You didn't provide enough information. For example, you didn't ask your
question in this post, so I have no idea what it was. It is important to
provide as much information as possible about the problem in order for
someone to figure out what the problem is. Remember that the Internet is
world-wide, and people communicate differently in different parts of the
world. So, more information is better.

2. The question has been asked and answered many times before. Be sure and
read the newsgroup first to be sure you're not asking one of these types of
questions.

3. The answer is obvious. For example, you may not have looked in the Help
file for your answer before asking someone to answer it.

4. Bad Netiquette. It is important to remember that participation in these
groups is purely voluntary. Be sure and be polite. Also, cross-posting and
multiple posts of the same question will make people  and unwilling to
help.

5. Nobody knows the answer. This happens occasionally. People can only
answer what they know about, and everybody knows only a portion of what can
be known. This happens more often with beta or newer software.

There are a few other reasons, but I've covered the most common.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Ambiguity has a certain quality to it.


"BV" <BV@discussions.microsoft.com> wrote in message
news:4947AA1B-CD26-42EC-B6B7-F71DCD04EDCD@microsoft.com...
> It does not seem to be the best place to be answered.
> Any suggestions?

My number one reason I don't answer, is because I keep hitting that stinking
reply, instead of reply group and I can't stop it. If I could hook about 20k
volts to my chair and fry my fanny to a smoking blackened piece of meat, I
would eventually learn, but I never learn till I go through the tortures of
the dammed for about a year. Because of this, I go through a few newsgroups
answering, and by the time I'm half way through my third, I'm doubled over
with stomach pain so bad I feel like I"ve swallowed drano!!

I really really need some program that can run in the background that puts a
little window that says in front all the time, which blanks out that button
so I can't hit it, or hacks my Oaflook express so I can't reply via email.

The oaf in oaflook is me btw.

Another pair of programs I would love to see and I think they might be
possible in Visual Studio are ...

1. A program that might act as a wrapper for another program where it would
intercept my clicking on the X button by accident. I am forever, setting up
a particular order of applications on my toolbar because my vision stinks
and I tend to "thrash" like a hard drive trying to find stuff that is in
front of my face forever, until I am shaking with rage. I find that by
opening up apps that are commonly used together, in a particular sequence, I
cut down on this thrashing till my eyes bleed phenomenon greatly, but I am
forever and always shutting down an app I do not want to shut down, and so
then I have to shut down everything and start them all up all over.

2. Windows has a fine startup folder, but I sure would love to see  a
shut-down folder, a folder. Just as there are certain tasks that I might
wish to do on start up, there are other tasks that I might want to do when
shutting down, such as clocking in and clocking out. I have no problem
clocking in, but clocking out, I can't remember even if someone held a gun
to my head. Other must-do before leaving tasks would also be things to do
before going home for the day.

"Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
news:e6tGbcRaFHA.2756@tk2msftngp13.phx.gbl...
> Well, I'm going to guess that you asked a question that didn't get an
> answer. There are several reasons this might happen. Here are some of
> them:
>
> 1. You didn't provide enough information. For example, you didn't ask your
> question in this post, so I have no idea what it was. It is important to
> provide as much information as possible about the problem in order for
> someone to figure out what the problem is. Remember that the Internet is
> world-wide, and people communicate differently in different parts of the
> world. So, more information is better.
>
> 2. The question has been asked and answered many times before. Be sure and
> read the newsgroup first to be sure you're not asking one of these types
> of questions.
>
> 3. The answer is obvious. For example, you may not have looked in the Help
> file for your answer before asking someone to answer it.
>
> 4. Bad Netiquette. It is important to remember that participation in these
> groups is purely voluntary. Be sure and be polite. Also, cross-posting and
> multiple posts of the same question will make people  and unwilling
> to help.
>
> 5. Nobody knows the answer. This happens occasionally. People can only
> answer what they know about, and everybody knows only a portion of what
> can be known. This happens more often with beta or newer software.
>
> There are a few other reasons, but I've covered the most common.
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> Ambiguity has a certain quality to it.
>
>
> "BV" <BV@discussions.microsoft.com> wrote in message
> news:4947AA1B-CD26-42EC-B6B7-F71DCD04EDCD@microsoft.com... 
>
>

FYI did an MSN search on "disable close button on window", found this
shareware program: http://www.privacyinspector.com/soft_102387.html :

"Description: WinTopMost put topmost automatically any window and/or disable
its X close button (window's top right corner). Put topmost any window or
comme back to a "normal" (non topmost) window Can set topmost automatically
all windows with captions containing specific strings. WinTopMost intercepts
windows captions when programs are running. Disable or enable the close
button of any window. Can be used in command line."



"Garry Freemyer" <garryfre@pacbell.net.byespam> wrote in message
news:e1vuWw3aFHA.2996@TK2MSFTNGP10.phx.gbl...
> Another pair of programs I would love to see and I think they might be
> possible in Visual Studio are ...
>
> 1. A program that might act as a wrapper for another program where it
would
> intercept my clicking on the X button by accident. I am forever, setting
up
> a particular order of applications on my toolbar because my vision stinks
> and I tend to "thrash" like a hard drive trying to find stuff that is in
> front of my face forever, until I am shaking with rage. I find that by
> opening up apps that are commonly used together, in a particular sequence,
I
> cut down on this thrashing till my eyes bleed phenomenon greatly, but I am
> forever and always shutting down an app I do not want to shut down, and so
> then I have to shut down everything and start them all up all over.