Search results

boblarson - Ah, thank you. Unfortunately, I know that I could create seperate IDs and link Systems to CashFlow and Parts to CashFlow seperately, I was just hoping for a way to use one unique ID throughout the whole system, just changing the syntax of the ID. For example, a System would have the...

Ah, thanks for the advice! rburna904 - Well, there will never be more than any one item with a Serial number - the serial number is unique among every System or Part. The other thing is, I cannot change whether the relationship type is One-to-One or One-to-Many boblarson - Thank you for the...

I've removed those options, and changed the name to "SerialNo", but I still have the same problem. I have already filled the database with some data; "Systems" and "CashFlow" have some entries with identical "SerialNo" fields. I can create a relationship by dragging the "SerialNo" of "Systems"...

Hi all, I'm just putting a database together, and I'm having a relationship "issue". It's fairly simple right now, but I'm not sure if you can do what I am trying to do.. Basically I have, so far, 3 tables. Each one has a primary key "Serial #". There's a "Systems" table, a "Parts" table, and...