Printing One Item Per Page

[BallCapBob]

Greetings all!

I've looked (really) but I have not found anything close to a sollution yet. I must be missing something.

I have 2 related tables(Customers and Equipment) where each customer can have more than one piece of equipment (the amount varies for each customer).

I need a report that prints out the equiment information, one per page, with the customer information on every page and a Job Number (auto generated, but same for each page) on every page. Basically like a Service Ticket. One ticket per each piece of equipment, one customer per multiple peices of equipment.

I'm not asking for a complete tutorial but if someone could give me a clue or point me in the right direction I would appreciate it.

BcB

[comment]

I got a bit lost towards the end, but I think you want to start with a form layout showing records from the Equipment table. Then just place any fields you want from the Customers table on the layout. Finally, double-click the "Body" part label and turn on 'Page break before each occurrence'.

[BallCapBob]

Sorry for the delay in responding. I get called away sometimes for many days.

I've been thinking about it and believe what I really want to accomplish is to save a found set to a new table. In the new table, each machine is listed seperately so if a customer had 6 machines, there would be six records with the same customer, but different equipment.

As the records are added they would be given a common job number then I would print the records from there.

Or

I could reverse that and give them all individual job numbers (haven't decided yet).

This would also allow me to keep a history for each unit.

Does this sound right, or am I making it too hard?

[comment]

I thought you already had separate tables for Customers and Equipment. I am not sure what role jobs play in this - a little more background would be useful here.

[BallCapBob]

OK, let me see if I can make this clearer.

I have a two tables, customers and machines. The two are related in a one (customers) to many (machines) relationship. I provide periodic maintenance service for these machines. When I go to service this equipment, I handle one customer at a time and all of their related machines. One customer can have as many as 15 machines, and as little as one.

What I am attempting to do is to print my service tickets with the customer and machine data already on it. Since each machine requires its own service ticket, a customer could end up with as many as 15 separate tickets for the performed service. At this time I use preprinted forms and each ticket has it's own number on it. I usually take the first number in that series and make it the job number for that particular performed service. And now I am trying to use NCR paper to print my own forms for use.

I have already created the data input form using a portal to displayed the linked equipment and the form (Service Ticket) I use to print out the service tickets for the individual machines. This works (sort of). When it's time to print out my tickets, I switch to the other form (Service tickets), do a search on the customer field and print the resulting records. This works fine, albiet a little klunky.

However, what would be really handy is to be able to print a single (same) job number on each printed form and the date (which is usually the following day after printing the tickets). I need to have the job number auto increment as I use the number elsewhere in my accounting. I would also like to have the tickets available as a history so that I may review and edit data from previous service.

My thought is to copy the found set of records to a new table, add the job number and the date in this new table that I can also use to add or edit the data as mentioned.

So to summarize; I need one number printed on each set of forms I print and the date.

I'm sorry for the confusion and I hope this is clearer. I can only hope my business grows enough one day so that I may hire some talent to do all this monkey-motion for me.

Thanks.

[mr_vodka]

To me it seems as though you would need the following: Customer, Equipment, Job, LineItems. If the equiptment is standard across the various companies such as a certain type of printer, copier, etc. I would even go with a CustomerEquipment table and store the Eqip info in its own table.

[comment]

At minimum, you need another table for the service tickets. This table would be related to the Equipment table by EquipmentID (one machine has many service tickets). An auto-entered serial number field would ensure each ticket has a unique TicketID.

You may also want to group service tickets by job (one job = servicing all of one customer's equipment once). That would require another table of Jobs, and the service tickets table would become a join between Equipment and Jobs (each ticket belongs to one machine and to one job).

Creating the tickets is more of a user-interface issue, and there are many options available here - once you get the basic data structure right.

For example, to create all of one job's tickets in advance, you could find the customer's equipment records and import them into the service tickets table.

Or, you could just create a new job record and ssign it to a particular customer. That would enable you to view all of customer's machines in a portal to Equipment from a layout of Jobs. Then you could click on a machine record in the portal to create a new service ticket relating to that machine and this job.