>>>I would like to have a feature that allow report detail to call another form, something which most commercial softare does. For example, when viewing invoice listing, user is able to double click on a line to pop-up the document.
>>>
>>
>>Rather than a report tool, you might try creating DHTML, which can include hyperlinks that can call forms and the like. Using the IE Web Browser control in conjunction with VFPCOM allows you to add VFP code to browser content events, which would let ytou launch a form from a hyperlink, or whatever - Ken Levy spent an hour and a half yesterday showing of the real power of VFPCOM in detail...and some of it may have sunk in. You don't need a repoirt writer, you need VFPCOM, and to use a browser control to handle the display of the data rather than a report writer tool, which creates static printed output.
>>
>>>Does Crystal report or other tools do that?
>
>Hmm... too bad I am in Singapore.
>
>What's VFPCOM? ActiveX control?

VFPCOM is an OLE Automation component usable within VFP (5 or 6) which can eamine and export the events of a COM/ActiveX object to simplify building an interface with VFP, and then can bind a VFP object that uses that interface back to the COM component so that events of the component call the VFP code you write. So you can access IE events, or MSCOM32 events, or to other things and bind VFP code to the events. You can download it from msdn.microsoft.com/vfoxpro/downloads

>
>Anyway, HTML's problem is the font size. I cannot present a report-like (WYSIWYG-like) HTML page. That's why if given a choice, I would prefer report.
>
>So much to learn, so little time...

Reports aren't dynamic and interactive. Good luck.