Barbara,

Yes, I have considered Word, and would prefer to. It's what I'll use for printing, etc. I do, however, want to be able to display a scrollable report within an area of my programmatically controlled form. When I tried a Word document in an ole container for this I ran into 2 issues. First, no header displays. Second, there are no scroll bars. I'd love to use a simple grid for this display, but need some decent banding capability with at least minimal summing/totalling. Perhaps I can achieve what I need with an embedded Word document but (as is painfully obvious from many messages posted here, as well as my own experience) there isn't much out there in the way of documentation/samples.

Isabel

>Have you considered using Word for all of this? You can develop your document from your data and then load
Word outside your app. Users can edit/save/print/ignore the output with no further work on your part.

>Barbara

>>Barbara,
>>
>>I want to do 2 things. On the back end, I want programmatic control over the creation of the report, using
PEMs of the object, and the ability, certainly, of sending my VFP data into the object. I'm not worried about the
object directly reading from a VFP source, as there are lots of ways to move data around. There will be banding,
minimal calculation, and no graphing.
>>
>>On the UI end, I want to display a view-only report in a section of the form (this is an ActiveDoc app). Simple
header, no footer. The form will have options for making the view area bigger/smaller, but no zoom, and I need
scroll bars in the report area. I want an in-process object that does not take over the whole screen or launch
another app.
>>
>>I am not concerned with printing, because I will have an option to create a Word document for that prupose -
my users will frequently want to tweak the printed output. That's why I started with looking at using a Word
document in an ole control.
>>
>>Thanks,
>>Isabel