Mike,
In this case I was working with an RTF in the form, and wanted to use it in a report form. I was only commenting that in my past (about 20+ years ago), I had to write a report in FPD2.6 that used embedded HPGL calls directly to the printer to control the output. It had some complex "white spacing" algorithm that I had worked out so that people with thin resumes didn't look so thin by spreading out the gaps between lines. (This was a client requirement, COAS at Indiana University job placement for students). The only way to do it was to get gritty with HP laser language.
I would certainly prefer not to have to go to that length, but if doing it programmatically is the only way to go, then I will consider it. I don't fully grasp your code, but if as Olaf mentions it's only to print the content of the RTF memo, that wouldn't give me everything I need for the report.
Olaf,
I know it seems like a lot of data, but it's not quite as bad as it seems. There are multiple records with multiple memo fields (just plain text now, but I want to convert them to RFT if I can get it to work). These combine with other image data (photos) that get output to PDF (just print to PDF, instead of a printer). So these docs end up being usually around 50 pages. We used to use Word and Excel, but we can't utilize the data then, and we have to do a bunch of work for calculations and comparisons by hand then, and that's highly error prone. So our approach instead is to break down the data into groups i.e. Mechanical, Electrical, Architectural, Telecomm, and throw that at a report form which has, as you suggested already, a summary, but then provides detail bands for the rest. The text then is just plan text. It would be much better if we could use an RTF control, so the output has a more "Word Document" feel to it.
I know our requirement may sound crazy to you, but for us it's a huge competitive advantage in time and consistency. Now we'd like to make it prettier. (I think I mentioned before we're shifting more to "core functionality is done, now it's time to make it pretty" in the development cycle). Hope all that makes sense, and thanks for all the suggestions, I'm just now trying to weigh the RTF vs. Office Automation, vs. report writing in code, vs. what we have now. I barely sleep anymore, and I'm looking forward to getting this really battened down finally so I can return to a normal life, and maybe even have a holiday...
Hi Griff,
I just got the ZIP downloaded, so will take a look thanks.
On the plus side, it gives me options to think about, and my thanks to all.
Best Regards,
Scott
MIET, MASHRAE, CDCP, CDCS, CDCE, CTDC, CTIA, ATS
"Everything should be made as simple as possible, and no simpler."
![[hammer] [hammer] [hammer]](/data/assets/smilies/hammer.gif)