>>>Thanks Gary. Looks interesting. Gotta love how the standard edition does not support DOCX nor hyperlinks. I'm curious about how >>you are using the control. Are you keeping letters in DOC files while using the control to import the DOCs for editing and >>for 'exporting' to PDF'? Does this allow you to avoid having MSWord installed on the workstation(s)... bypassing Word automation? >>Are you using the content for html emails?
>
>I have built the control into my apps, so client can either use MS Word/Open Office to create .DOC files (I have avoided .DOCX for the moment) for "import" or they can edit direct in my app. I store on disk as .DOC files.
>
>I no longer use Word automation as a) clients had mixed versions of Word causing incompatabilities b) some clients went over to Open Office (or nothing on some workstations) c) by using TxTextControl I could save as PDF and attach to an email or save as HTML and copy to email body (both of which I offer clients).
>
>So our "Mail Merge" functionality became more flexible and more reliable. We wrote it as a "generic" add in and it's now incorprated into any application we develop as a standard feature.
>
>
>Gary.

Very nice. I currently use an nBit control for html email msg editing but that has issues on win7 boxes. so i also have a webbrowser control version for the win7 boxes but that has its own set of issues. and i use word automation that needs DOC-to-PDF functionality. this sounds like it could replace all that. thanks much.