Jim,

>The guy really can't win, can he...
>
>When he says "BUG" in the thread title (some) people jump all over him for reasons unknown but consistent.
>
>When he carefully avoids the word "BUG" in a thread title he is told that he is saying it is a bug anyway!

You are just so far off base here it's not even funny. What's the issue with me saying that his "problem" is not a bug in VFP. It's a factual statement Jim.

>Another thing that I might as well clear up while I'm here...

That's called "gunny sacking" Jim, you should deal with your issues when and where they come up, not days or months later.

>In another thread you repled 'all you have to do is SetFocus to the grid in init' and I asked if this was documented or a workaround or what and you said it didn't matter to you. Well, it DOES MATTER, a whole lot, to other readers. If it's a documented thing then they know they can rely on finding it there should the situation arise, BUT if it's a workaround then they may want to 'file it away', possibly in some list they keep or possibly in a UT folder or possibly in the UT 'Favorites' list or possibly just as a mental note or possibly...

Now let's go back to that thread and take a more careful look at my reply http://www.levelextreme.com/wconnect/wc.dll?FournierTransformation~2,15,895879 ...

All I'm doing is posting another alternate solution to the posted problem Fabio is having. If you don't want the grid to have focus you can move focus to the first control in TabOrder after setting it to the grid. I don't particularly care how it is classified.

So I said "posting another alternate solution" doesn't that mean workaround to you? My alternate solution was significantly less code that what Fabio was saying was necessary.

As far as the classification goes, I really don't care if the original problem is a bug in VFP, a bug in the docs, or a by design issue, or however whoever wants to classify it. Since it's going to be a significant amount of time before it'd be changed in VFP in any case, it's the best help to the most people out there to post solutions, alternate solutions, and workarounds so that they can get around the problem today.

>In other words, your reply was curt and far less helpful than it should have been.

Sorry that my replies aren't meeting up to your standards of length and content.