CHMlib Logo Leading Translation Management System for Translation Agencies, Top Translation Management Software for Freelance Translators, Time Tracking Software, Word Count, Character Count and Line Count Software, Computer Assisted Translation Tool for Easy Word Count, Clipboard Character Count Software, User-Friendly Translation Memory Software, Terminology Management Software, Terminology Management Server, Microsoft Glossary Software, Dictionary of Acronyms, Social Network for Translators and Translation Agencies, Acronyms and Abbreviations Search Engine, Russian Translation Lab, Ukrainian Translation Lab.
You are reading help file online using chmlib.com
CrisisHelper - First Aid in Tough Times of World Economic Crisis


_bm0 Rave Reports Visual Designer

Headers

Top  Previous  Next

QUESTION:

My report MUST have the same header and footer on EACH page, regardless of how many detail records there are for the master record.

 

ANSWER:

The solution is put the items you want on every page directly ON THE PAGE not in a band. Pardon the caps. Just wanting to emphasis that you do not have to do anything or everything with bands in a region. The main thing to get across is that Rave is a Page-Based designer and exactly what that means.

 

For example, if you are doing a form style report, like one of the IRS forms, etc, you don't need to use a region at all. We have seen some RAV files that were ALL form style and none of the reports had a region. Of course, if you are doing a "form" report, you may need to use the "DataCycle" component to move through the data tables. Remember, the "DataCycle" should be the first component in the tree list.

 

If you are doing a band style report then you use the region component as a "holder" for band components.

 

If a component has to be in a region, it will not let you put it outside of a region. Try and put a band directly on the page - can not do it. Try other components, Text, DataText, DataMemo etc. and they will go where you like. Of course, you have to assign the DataView and DataField properties on the data driven components as you normally would.



You are reading help file online using chmlib.com

If you want your help file to be removed or added please send e-mail to chmlibcom@gmail.com