Page 1 of 1

Tutorial showing how predefine document layouts

Posted: Thu Jul 15, 2010 1:08 am
by agent86
I want to design "canned" reports that can be used over and over again.

I want a master document that is broken up into 4-6 quadrants, 2 across, 2-3 down. There will be letterhead at the top of the page

The content for each quadrants will come from the dbrichviews and pictures. The client will enter the data in the individual dbrichviews on a seperate entry screen, not into the master report. They will also have pictures and charts that will be displayed in the quadrants. I would imagine that the text will be filling the left quadrants, the pictures and charts on the right quadrants. I want to store the report template definitions so a client can seect them in a dropdown. There is a foreign key that ties all the dbrichviews together on the master report.

Because I have predefined which dbrichview goes where, I can reuse the report template. I then will click a button that tells the program to move the text from the dbrichviews to the master document.

Are there demos or tutorials that can get me pointed in the right direction with this. I hope I was clear on what I am trying to accomplish.

Posted: Thu Jul 15, 2010 10:14 am
by Sergey Tkachenko
May be you can create a template as a document containing table (TRVTableItemInfo), and data will be placed in table cells?

That just might work!

Posted: Thu Jul 15, 2010 3:24 pm
by agent86
I didn't think of that! I'll give it a try.

Thanks...

Table cells expandable?

Posted: Thu Jul 15, 2010 3:27 pm
by agent86
If the text entered into the cell exceeds the number of rows in the cell, will it automatically expand to display the content without scolling that cell. It would be OK if the cell expanded to the next page. I won't know how much text will be in the cell. Some may contain a few sentences, others might be multiple paragraphs.

Posted: Thu Jul 15, 2010 4:04 pm
by Sergey Tkachenko
Yes, this is the default behavior - the cell has enough width and height to show its content.
About the specific implementation: see the demo in Assorted\Fields\MailMerge2\. It does almost what you need: a template with fields, field content is a document stored in db.
See the image:
http://www.trichview.com/shots/demos/mailmerge.gif