Hi Eric,

>It is kind of a unique situation. They really dont send out invoices per say...

>My plan right now: have a seperate sequentially numbered list of the sponsors in the
>same order as the bills so they can then tell what ones are actually missing.

I thought it was something like that. Normally your invoice numbers are as important as your check numbers as there needs to be accountability for each and every one of them. After all, your invoice is your business' legal notification to your customer that they owe you money.

Anyway, if you want to add another number that is printed on the "invoice" itself for the purpose of rectifying a mechanical failure situation, that sounds reasonable to me!

Hugh

>>Some questions: If the invoice numbers are randomly generated how would you know if one was missing? If it's not important to you to tell if invoices are missing, why send them in the first place?
>
>It is kind of a unique situation. They really dont send out invoices per say... more like a billing statement that gets sent only twice every year. Let me explain the program a little so you understand. It's a program for Big Brothers Big Sisters Bowl for Kids event. You may have heard of it. Anyway, my main tables are: bowlers, sponsors, and a pledges. The pledges table relates the bowlers and sponsors tables (many to many releation). So my bowler and sponsor ID's are randomly generated. Now the bills that get printed, are bills that get sent to every sponsor. So there really isnt any invoice number. They just need to generate a bill for each sponsor.
>
>You do make a good point though, that if they are not sequentially numberd how will you tell what ones are missing. My plan right now: have a seperate sequentially numbered list of the sponsors in the same order as the bills so they can then tell what ones are actually missing.
>
>Does that make sence? ;)
>
>Thanks for the tips.
>
>Eric