Hi Craig
1. Because VFP9 would be backward comaptible. So new functionality should run with old design. Do you suggest that VFP9 new report designer output options will run only with newly created reports. Remember that my reports run inside VFP without problems.
2. Because during coding such fuctionality - if something has to be changed in VFP internals it can be done only if Microsft VFP team was preparing such functionality. Third party vendor must be waiting for service pack or next version of VFP.
3. It is much more easier create additional funcionality having described
in previous point possibilities than coding around black box.
4. VFP team members have more knoledge how VFP internally works than people from outside.
5. I believe that Microsft more carefully test its product.
6. Compare for example "code refrences tool" out of the VFP8 box with other external search tools that was available before VFP8. The internal tool is far far better.


>What makes you think that if PDF was supported out of the box that it would make proper PDF outputs for your reports?
>
>
>>Hi, Craig
>>I believe that VFP9 will be backward compatibile and that is the reason why I wanted to have PDF output option included in VFP box. My trust in future additional applications made by 3-party is very limited - this is based on my expierience while evaluating tools that render VFP reports definition (not simple) to make PDF output. Maybe the Ken mentioned hooks will help made such add-on. But today I have no warranty that such products will exist and that they will make proper PDF output for my reports.
>>