Carl,

Thanks. This is very helpful info.. especially to know about the limitation with tables.

Can you tell me a little about what you mean by 'word specific RTF extensions'

Thanks.

>

Hi David,
>
>I'm using both VisDocs and TX Control in a vertical app.
>VisDocs is pretty good and the timeliness to tech support questions is acceptable also. Source code is included and by browsing the meta tables it creates from the RTF template, you can easily aquaint yourself with the RTF tags that Alex mentioned in his reply.
>
>I'm only using TX Control for printing because I can't guarantee that Word is installed. It is much faster at printing than using Word. One real limitation is that TX Control does not support the Word-specific RTF extensions and I was very disappointed with the way it handles tables. Their web site says that there are only minor issues but that's a bit misleading - empty rows/cells are omitted in much the way HTML tables are handled so it's not good for forms with cells that may or may not contain data.
>
>For regular documents the combination works well but if you're using tables beware that the TX Control won't necessarily (likely won't) print the way you want it to.
>
>HTH,
>
>Carl
>
>>I am looking for some advice on the most straightforward way to implement modifying/mailmerging and printing RTF based legal documents (or other documents with variable data) through a VFP (or .net) application.
>>
>>Here are my requirements:
>>
>>1) For starters (phase I of the project) all I have to do is print an RTF document as is, without modifying it. Thats it - select the existing RTF file from a grid, open it and print it.
>>(The client has supplied me with existing RTF documents - in the places where variable data goes - they have the string "*.*". I am guessing that some other program they used filled these occurrences with the proper data based upon the position - e.g. first, 2nd or third occurrence of *.*)
>>For phase one we will just hand change the RTF files to have '______' where appropriate instead of *.*
>>
>>2) For phase 2 I need to take these existing RTFs and map each document to some sort of data entry form or wizard, and then have the application merge the data.
>>
>>3) Right now I don't have any requirement to 'build a word processor' inside my application, or do any fancy editing of the RTFs. I'd just like to be able to create/modify the RTF's myself using word.
>>
>>
>>Here are my questions:
>>
>>1) I have seen the advertisements for VisDocs 2.0 at www.codemine.com
>>Has anyone tried this/ had good results?
>>
>>2) The codemine authors recommend using their tool in conjunction with TX Control. Does anyone have any experience with this product.
>>
>>3)Are these tools overkill for my stated requirements? I know that Microsoft has a free ActiveX control for RTF. Is this control too limited to accomplish what I want or will it easily do the trick? I don't want to spend too much time investigating it if it won't easily give me what I need.
>>
>>4)I don't want to spend a lot of money on tools for this project if I don't have to, but will if necessary.
>>
>>5) In the past I did some word automation projects. I could convert these RTF's to word and use word automation instead - but then the client would need word installed on every machine that uses the application - and, I have heard that word automation is slower. Any other input as to the advantages and disadvantages of word automation vs RTF?
>>
>>TIA for any suggestions