April 10, 200124 yr Newbies This one is either so easy that the simplicity of it bewilders me or so complicated i am bemused - either way i need help. I have two db's a simple relation... based on the fact that the product description can change alot... so the description is built in the second db out of fields containing the elements of the product... with me ?... using a calc... SLength & "'" & " " & "x" & " " & SWidth & Inch & " " & Weave Type & " " & "Recovery Strop" & " Rated at " & Rating & "kg's, or double that rating for towing." Then ... in the invoicing db... i perform a lookup based on the selection of the product field... [which is also a menu list - heres the kicker - built out of the product db's description [and calculated field]]. Problem is that on one hand i can't do that because the field cannot be indexed because its a 'live' calculation and on the other hand the description is already not a live field as its an auto enter calculation... ! i know i know its wrong... but i need a leg up ... so to speak. HELP ? Regards Guy
April 10, 200124 yr quote: Originally posted by ixplorer: This one is either so easy that the simplicity of it bewilders me or so complicated i am bemused - either way i need help. I have two db's a simple relation... based on the fact that the product description can change alot... so the description is built in the second db out of fields containing the elements of the product... with me ?... using a calc... SLength & "'" & " " & "x" & " " & SWidth & Inch & " " & Weave Type & " " & "Recovery Strop" & " Rated at " & Rating & "kg's, or double that rating for towing." Then ... in the invoicing db... i perform a lookup based on the selection of the product field... [which is also a menu list - heres the kicker - built out of the product db's description [and calculated field]]. Problem is that on one hand i can't do that because the field cannot be indexed because its a 'live' calculation and on the other hand the description is already not a live field as its an auto enter calculation... ! i know i know its wrong... but i need a leg up ... so to speak. One word: ProductID! You should give each product a uniqueID, regardless of any other data. Make it an alpha-numeric code that is meaningless to the actual product, and use this for all of you relationships, lookups, etc. I use the following for my IDs: Status ( CurrentRecordID ) & "-" & Status ( CurrentDate ) & "-" & Status ( CurrentTime ). This give a meaningless, unique ID, that is virtually unduplicatable.
Create an account or sign in to comment