>>Hi BOb,
>>
>>I would add MsWord to your short list It leaves the programming on the VFP side, so you can massage the data as you want. And it's a snap once you get used to it. There's a problem, though, the lack of precise documentation from a VFP developer point of view. There are lots of examples here and there, but nobody has yet come with a full how to.
>>
>>José
>
>The problem with using word is that all the reports would have to be created programmatically. This would allow for no end user customization. Also, we have over 200 reports in our ap, so hand coding them is not feasable, with a report writer we can have QA and support people held us write the reports.
>
>IF I am missing something let me know. And, thanks for the suggestion.
>
>BOb

I see different things here. First is the creation of the view that will contain the data. It has to be done by someone who has the skills and as flexible as possible, iow with the necessary parameters.

For the command of the report itself you are right that it must be done programmatically. But I've seen persons with virtually no VFP knowledge be able to achieve this successfully provided they had a good template.

Now, regarding the end user customization, you give them full access to it. They can change the position of the fields, fonts, page layout etc, provided they don't eat the bookmarks.

José