Re: Creating and saving IDs - is there a theory?

Lior Messinger wrote: > > Hi, > > We are designing a project where we need to create, save and then verify > huge amounts of IDs (or serial numbers), for inventory items. We need to do > the saving part and the verification very fast, on a server. This is done > to verify that the items are not faked. Seems to me: 1. a serial number is unique therefore it must be the key. 2. a serial number is created against a specific inventory item therefore datafield 1. 3. a serial number is shipped against an invoice there fore a cross reference to customer-master datafield 2. If your file is sized correctly... access to a specific serial number should almost instant. So.. In our inventory receipts program (work order or purchase depending) create the unique serial number and create the record in the serial table. Shipment program assocates all serial numbers with customers. Now if the ownership of a serial number can be transferred to another owner thingsgets a little more complicated in that 1. the serial is valid but the owner (datafield 2 ) is incorrect. This seems to me to be a procedural problem. Note: alternately you could wait until the owner send you his waranty card to fill in datafield 2. in which case you'll probally never have an accurate picture cuz who sends in the cards? jr! ---------------------------------------------------------------------- Jim Roberts jroberts@interaccess.com James Roberts Computer Consulting 847/658-9409 ----------------------------------------------------------------------