Thanks Vaughan for your response.
I guess I should have mentioned that those
headers represents departments under which
highschool classes fall. They are summary
information that is shown in a student's
transcript.
Student #1001 take classes in English, Math,
Science, etc. These classes falls in different depatements.
When a transcript is viewed or printed the
information must have a department header followed by classes that fall within that department, then on to the next sent of classes with its dept header. Different students will have different classes and thus different department.
Summarizing the data by student id and department is not the problem. Currently we do this using COBOL on a mainframe. Someone got the bright idea to migrate this to the desktop using FileMaker. Everything is working except getting the print to go to another column when there is too much for one column.
I am fairly new at this FileMaker stuff so am having a problem getting it all sorted out.
If you can shed more light on a solution to my problem with this additional information I will appreciated it. If not, thanks anyway.
I am think of getting the boss to switch to MS Visual Basic which I know something about.
Of course that cost more money.
James
James
quote:
Originally posted by Vaughan:
Are "Header A" etc separate fields? If they are then I'd have to say that it's a bad way of designing the system.
Think about how magazine articles are written: each article has a heading and a story, an author, etc. A "database magazine" data structure should reflect this: each article is a separate record, each record has a heading, bodym author etc.
The layout only needs to be simple, because it will just be printing out the current found set of records.
So to answer your question, yes it can be done, but only if your data design is suitable. Keep it simple!