jasons78
asked on
Getting error "Invalid field definition 'Customer Service ID' in definition of index or relationship
I keep getting the above error when trying to create a relationship between fields called "Claim ID" and "Customer Service ID". Both fields are Autonumber primary key fields, and I have Enforce Referential Integrity checked when trying to create the relationship.
I tried checking Access help, and all I get is:
Possible causes:
· The field name you've specified might be misspelled. Check the spelling of the field name.
· The field type you're using is a Memo or OLE Object, which cannot be indexed.
I'm pretty sure everything is spelled correctly, and the field type is Autonumber, not Memo or OLE object, so I don't think that is the problem.
Anybody have any suggestions?
I tried checking Access help, and all I get is:
Possible causes:
· The field name you've specified might be misspelled. Check the spelling of the field name.
· The field type you're using is a Memo or OLE Object, which cannot be indexed.
I'm pretty sure everything is spelled correctly, and the field type is Autonumber, not Memo or OLE object, so I don't think that is the problem.
Anybody have any suggestions?
miqrogroove
You cannot create a relationship between two AutoNumber fields!
If you need further help then you will have to tell me what type of relationship you are trying to create. i.e. How are claims and customer service connected?
ASKER
I'm creating a db for file audits. I originally had everything in one table, but since there are 5 general areas that a file is audited on, it seemed more practical to break up that table in to the 5 different areas. I now have 6 tables named tblClaimInfo, tblCustomerService, tblInvestigation, tblDocumentation, tblPayment, and tblRecovery. TblClaimInfo holds the general info about the claim; claim number, branch office the file is in, adjuster's name, etc. The other 5 tables hold the criteria the file is audited on.
So basically all the information needs to be linked back to the claim number, but I don't want to use the claim number as the primary key, just in case sometime in the future the same file gets audited twice.
So basically all the information needs to be linked back to the claim number, but I don't want to use the claim number as the primary key, just in case sometime in the future the same file gets audited twice.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.