At our Young Eagles events, we've been using the certificate printer to make nice looking remembrances of the flight for the kids. The process we use is that when they arrive, and have the form for us, we assign a sequential number, enter preliminary information into the program, and then give the forms to the person assigning kids to planes.
The pilot signs the form, and writes the tail number on the form too since pilot signatures are worse than doctors'. It gets returned to the registration table. When the kid lands and goes back to the registration table, we go back into the program to link the pilot with the kid, and print their certificate. We don't print the certificate until they return to the table, since some just leave.
The problem is that new people are coming in when others are waiting for the certificate creates a bottleneck. I'm afraid of data corruption of having two computers connecting to the same Access database if we have one computer for registration making new records, and another for editing that record and certificate printing.
Has anyone tried this, or have any better suggestion?