The id value (an 8 digit number) of the customer who has booked this. Note that for this application, you should assume that customers and CSRs know their customer ids. The system you are writing does not interact with these numbers, rather it simply records them. If this field is all blanks, the record is available for sale.
Right now, when the user decides to book a particular contractor the ID value is automatically generated for them before the contractor is booked. After successfully booking the contractor, the random, 8-digit number I've generated appears in the JTable.
I'm beginning to think now that I may want the user to actually enter the number themselves instead of generating it for them. Or, is it even important at all that this number is be displayed? In which case I can continue what I'm doing.
Originally posted by Richard Everhart: FYI... I've decided to prompt the user for their ID when the client gui is started instead of them having to do it everytime they decide to book a contractor.
That is wrong for URLyBird, I'm not sure about B&S, but each customer calling the CSR on the phone has a different customer ID. Therefore the CSR cn't just provide it a signon, its a per booking attribute.