Viewing 7 posts - 1 through 8 (of 8 total)
OK I see the advantages of a numerical ID for both my Vins table and my Orders tables.
So is it like this then?
tblVins
-------
VinID -- numeric -- Primary Key
Vin -- 17...
June 5, 2015 at 1:16 pm
I think you're getting lost in the verbiage/usage of PO Number
Our customer issues a PO Number (their purchase order number) to the MFG
One unique PO Number with X number...
June 4, 2015 at 1:53 pm
This concerns me:
You heard only part of the story. SQL has an IDENTITY property. This works in the same manner as an auto increment in Access.
You would use this...
June 4, 2015 at 1:44 pm
Well each client has their own PO number scheme, and they submit to us their order. Those Order Numbers come attached to each VIN from each manufacturer, we have 10+.
We...
June 4, 2015 at 1:12 pm
Thanks Michael for the advice, I will do some reading up on the site you advised.
June 4, 2015 at 12:59 pm
it is 1 to Many...
PO is issued for let's say 20 vehicles.
20 Vins fill that Order
Each Vin row has the POnum field
June 4, 2015 at 12:57 pm
So using two non-numeric fields as keys won't affect performance given the number of records that I'm talking about?
Also what about the field type Char, VarChar ??
(I just tossed in...
June 4, 2015 at 12:45 pm
Viewing 7 posts - 1 through 8 (of 8 total)