Report standards tend to be very specific to the company you're working form. They include things like specifications for what should be in the page headers and footers and where each object in those sections should be place, what colors and fonts will be used, report naming conventions, etc.
-Dell
A computer only does what you actually told it to do - not what you thought you told it to do.
It's a good idea to have a Version Number, also an author name and maybe department in the report header. Page number and file-name plus path in the page footer or report footer. Date and time in the report header, maybe repeated in the page header. (You can use 'OnFirstRecord' to suppress the page header for the first page, stop it duplicating report-header information.
Have a report title, this is settable from File > Summary Info.
You can create a 'model report' that others can copy. The 'template' function in Crystal does not do this: instead it imposes a style of text etc. on an existing report.
It's also sensible to have a standard for Formula Field names, maybe a range of prefixes for different functions.
For efficient running, as much selection as possible should be in the report selection, which mostly means that the server does it. Dates can be tricky and you may need to set them as SQL commands.
Make it part of your standard that poeple need to use Report > Performance Information to check that everything is running well.
Madawc Williams (East Anglia, UK). Using Crystal 11.5 with SQL and Windows XP
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.