>Hi Ed,
>
>>I'd disagree with the strategy here, Ed. This sounds like an ideal situation for Word automation - build the report as a Word document, and then pop Word up to make changes as desired.
>
>So you need to purchase and run Office? Why force that on a user if they don't want it? I always make sure, if I need somthing that only IE will do, I'll find another way so an NS user can do the same thing, ect.
>
>Note: I'd stick with the VFP solution because I do shrinkwrapped appications, unlike (I'm assuming) most everyone else here.
Hi Mike,
Since I would also think suggesting WordOLE my .2 cents. What John wants could be done in a number of ways :
-Report to a file (text based portions) and modify file in a form (I think this one is in close touch with what Ed (Pickmann) is referring as a scrollable form)
Actual report could then hold a memo (all text portion taht's being edited) and other stuff such as logo. I tried this option in a project and it works just as they want it.
-Set a field on report referring to a variable(s) and while preview windows is open go and edit in an editbox or alike that has controlsource as that memvar (preview nowait). I haven't tried this one. Just an idea.
-Use WordOLE :) This would be quite nice but you're right everyone doesn't have word.
-Use ExcelOLE (but again availability problem).
-But almost everyone have WordPad. Let them do editing in wordpad sending report to a file and opening in wordpad.
-Or everyone has RTF control. Instead of report writer use RTF editing. For RTF editing I would suggest instead of report designer using a series of ? to a file. Get the text to RTF and set font to Courier New before editing starts. He could then even parse the edited text to see what has changed if important.
-...?
Merry xmas.
Cetin
