STRTRAN(tcHierarchy, LOWER(THISFORM.NAME) + ".", "thisform.") was not robust enough.

>BTW, you didn't tell us, what the problem was. Could you please reveal if for my curiosity?
>
>Thanks.
>
>>A little bug in GHL is fixed. you can download a new version GHL 3.7.3.
>>The reason it ever came up was that you were not following your own naming convention, i.e named your form Phones, not frmPhones (along with pgfPhones, grdPhones, etc.)
>>
>>Anyway, thanks to you, it is more reliable now.
>>Just to add to what other's said - as most of the freeware stuff on UT and elsewhere, GHL is provided "as is" which is explicitly said in Readme.doc. That does not mean that it has to be fixed on demand at once, not to mention that the author may be busy, sick, on vacation, out of the country, or there is Service Pack X release scheduled in a couple of month.
>>
>>Regarding not using the utilities with no source code, I would say that according to this logic people should stop using ActiveX controls, any kind of add-ins or Windows itself... :)
>>
>>>John,
>>>
>>> If GH would come with source code, I probably would be able to identify the bug and fix it myself. Unfortunatelly, it comes without source code, so I can only complain, if I find problems, but could not fix them... I sent Nick few private messages about GH, but I assume, he just doesn't have an access to UT or e-mail during the time of the conference and I wanted them to be fixed ASAP, because you can imagine my frustration, when I tried to use class, which I liked so much, and it gave me unexpected errors.
>>>
>>> Therefore I wrote messages here asking for Help or confirmation, if somebody else saw these problems...
>>>
>>> I understand, that here it's a free class, which Nick wrote in his spare time and put for public domain, and I really appreciate it. But neverless it should be a bug free, or at least, bugs should be fixed, after they are reported.
>>>
>>> BTW, I usually find bugs in somebody else's code and sometimes it takes me a long time to find them in my own. Anyway, I can say, that I'm a good tester, so if somebody needs to test a new utility and I have a spare time, I can help to avoid bugs and problems...
>>>
>>> About LS: I make a suggestion about new regime, it doesn't mean, I ask you to spend time on it, if you don't want. You can send me the source code (I forgot, is it already included?) and I can make these minor changes and enhancements by myself. Besides, they are not that important, I just thought, it would be nice to have them...
>>>
>>> Finally, if utility or class is in public domain, I think, I have rights to discuss it and I can choose for myself, do it in private or in public. If I do it in public, some lurkers may benefit of this discussion.
>>>
>>> Once Nick explicitly asked me to ask question, which I asked him in private about GH, in the main forum, so he can answer on it and others would benefit...
>>>
>>> I saw here lots of questions about Nigel Coates class, several about Frx2Word, several about GH, and I don't think, they are unapropriate...
>>>
>>> Finally, as you may remember, I didn't send you bug reports in public... :)
>>>
>>> BTW, I didn't fix the bug (and I don't know, how to fix it without source code), but I just was able to make it work. Therefore I'm not sure, what was the reason for the error. Perhaps, Page.Active method does not allow to set focus on the grid (strange, though, that I can call a form method from Page.Activate, which sets focus on a grid)...
>>>
>>>
>>>>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.