>>>Thanks, but I trying to keep it as simple as possible. Using built-in features of FoxPro when available. I would prefer this approach over having to include additional dependencies. If I can not discover a natural means, I would rather forgo the option to have hyperlinks in the application all together.
>>>
>>>But thanks for the option.
>>
>>Using native FoxPro you could create a class which pulls out words from the memo field and displays them like how a word processor would, creating label after label with autosize = .t., using the text metrics to determine how wide each item is and where to place it. For those items which are parsed as hyperlinks (file: prefix, or http: prefix, etc), you could render them with the underline and alternate color font, use the hand pointer icon on them, and then BINDEVENT() to the Click() of that object and have it parse the object's caption and open it.
>
>Sounds interesting, but currently I have been focusing on other issues. This hyperlink is a more of a "it would be nice, if..." enhancement. When first purposed, I recalled the EditorOptions feature, noting to look into it. If it appeared to be anymore difficult to implement, I would rather defer it to a future version then postpone the release date. When it pops up again, I may contact you.


Sounds good.