>Ric & Mark,
>
> Ok, seems like I finally have some support. Actually, I tried all possible alternatives: I wrote e-mails, private messages here in UT and public message as a last resort. Nick must be tired of my questions...
>
>Anyway, the good thing is that this little bug was fixed. And as I said before and can repeat, I had lots of situations, when I caught bugs, which nobody else can find before... May be I was doing something wrong in the first place... :)

Little grammar correction.

>
>>From a 'rookie' point of view, mine :-), I will say I have always understood that DL's here are to be addressed here. While I have on occassion used private or EM to clarify some problems or instructions, I try to address the issues here first.
>>And BTW, I too have incorporated this DL in my apps... I would have been hard pressed to even find the bug in the first place. :-)
>>
>>Ric
>>
>>>Hi John
>>>
>>>I guess I partly agree with you because I have some really cool stuff I am too coy to put in the DL section because I am scared of the support consequences.
>>>
>>>However I think folks should know however that some authors only want to support in UT and not in email. Nigel Coates and a couple of others have said this.
>>>
>>>This of couse can be a bit confusing deciding which method to use. Since even innocent comments can come over wrong sometimes when uder pressure of work.
>>>
>>>I think its important early on to find the authors preferred method of support, this is something I have tried always to do myself.
>>>Nigel has a good idea in posting in his tag line that he only wants to support in UT.
>>>
>>>I hope to make extensive use of Nick's GHL class in my next app so I established with him in advance what ground rules he wanted applying and will stick to them (when I get round to writing it)
>>>
>>>The point I am trying to make is that folks can run the risk of catching some flak which which ever way round they seek support.
>>>
>>>Just my £0.07 worth :)
>>>
>>>
>>>
>>>
>>>>Hi Nadya,
>>>>
>>>>OK, I've meant to post a note like this for a while, but my work schedule has really got me brain-fried.
>>>>
>>>>To me personally, it can be really irritating to see public posts on flaws in my freeware content. I like being told of bugs privately so that I may choose (or not choose) to fix them. I don't like public posts on bugs along with the implied demand that they be fixed.
>>>>
>>>>Further on in this thread, you complain that it took you 2.5 hours to track down and fix a bug in the Grid highlighter. I'll bet that you were being paid by an employer or client for that time. Well, the much greater time that Nick spent to write this utility from scratch, document it, and post it was a donation of his to the VFP community.
>>>>
>>>>It's entirely his option and his private decision whether he puts in any additional time into updating the utility.
>>>>
>>>>The freeware and shareware posted here (and elsewhere) are going to have flaws. Most of us do not have the time or wherewithal to produce 99% bug-free utilities for the public domain. So we create utilities that have a reasonable amount of functionality and are reasonably bug-free.
>>>>
>>>>If you use a utility, the courteous thing to do is to privately alert the author of any problems you found ... and then try to fix them yourself. And then alert the author to the fix so that he or she can either incorporate them into the utility as an update or give you his or her blessing to upload a new and improved version.
>>>>
>>>>Take my LS utility for example: I understand that it's lack of structured ASCII output drives you nuts. However, I would hope that the whole concept would inspire you to write your own utility that maybe did things a little differently or better that you could upload here to share with all of us.
>>>>
>>>>I'm not trying to be harsh, but, please, this public harrassment of the tool authors has got to stop. Either take it private or fix the problem yourself.
>>>>
>>>>>I successfully implemented GridHighlighter in several my applications, so I decided to use it everywhere. Today I found this problem:
>>>>>I have a form with a pageframe called pgfDataDictionary. First page, called Page1, has a grid, called grdDataDict. I placed GridHighlighter on the first page, called it GrdHglt1, in grdDataDict I invoked it:
>>>>>

>>>>>with this
>>>>>   .parent.GrdHglt1.Highlight_Row()
>>>>>   ..
>>>>>

>>>>>
>>>>>When I tried to set focus on the grid, I got an error. Something like: "pgfthisform is not found". Well, I renamed my pageframe to pgfData, and the problem went away. So, if parent object has a name, similar to a grid name, (in my case, pgfDataDictionary & grdDataDict), it causes problems with GridHighlighter.
>>>>>
>>>>>May be it should be mentioned in ReadMe document, if it could not be fixed.
>>>>>
>>>>>Thanks in advance.