RTF Control in Clarionet.
I have a client who has been running a program across a WAN using Clarionet. System was written several years ago in Clarion for Windows 6.1 and has not been modified for several years.
Recently he wanted an additional feature so that the system would generate some documents.
I was apprehensive in making the changes so built a small additional standa alone program to test with Clarionet. The programs are all Legacy template initially.
I needed to add a window with an RTF text window so the system could open a template .RTF document, and replace some tokens, then produce a print preview of the letter at the client side PC.
I knew that the Clarion for Windows RTF control was not going to behave in a Clarionet screen, so this had to be built to run without showing the RTF window and without any Clarionet code. By starting with a generated procedure, I then placed several OMIT statements to exclude any Clarionet generated calls. Next I added all my INIT, Document Open and KILL statements to right after the OPEN(Window) statement. Then I did the token replacements and saved the finished document as an RTF file.
Back in the calling procedure, I then passed the document’s filename to a report procedure, and placed the RTF file into a detail/text (rtf) control. This report then generated and the preview was auto-magically transferred to the client side PC. Done.
Now that I had got it working in a stand alone EXE, and it all worked OK, I then moved it into the trusty DLL written about 6 years ago. This worked fine and nothing got broken.