Relationship error "invalid field definition of index or relationship"
Consultants Pay History
Invoice Slip For Client
The thing thats worrying me is I dont want to hand the database into my teacher for it to be marked and then he tells me that the relationships are wrong and I lose valuable credits.
I know you guys are busy but if I attach my database could you please take 5mins of your time to download it and have a check through the relationships to make sure the logic behind it is ok?
And if it is not to much trouble could you tell me which table to relate invoice too
Thank you for taking the time to report an issue.
What's wrong... Please write below.
Error 3409 pops on the append.rel statement. I've examined the index I created on the old table. The field name I used to create the index is the same field name used to build the relationship. Both fields are primary keys. There are records in both tables.
On a related topic, if I want to recreate a table that has been dropped for some reason, what I understrand is that I can create an index on the table before populating it with data but I cannot create a relationship to another table until the recreated table has data in it. Is that correct?
Does anybody knows how to control the the below msg to something like this through VBA:
"The Item: " & ItemNo & " already exists in the table."
instead of this:
"The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again."
What is the Err.Number for this error?
I already managed to create a relationship with the Employee ID fields in the Users table and the Hardware Asset table.
Of course now when I try to link the software table to either the hardware table or the user table I run into that annoying "No unique index found." error and now I'm stuck. Can someone give me a hand
The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the date in the field or fields that contain the duplicate date, remove the index, or redefine the index to permit duplicate entries and try again.
when I try to import a .csv file. I googled and could only find reference where there is a problem with autonumbering or an existing table field: [LINK]
This does not apply as I get the error when importing into Access 2007 a new .csv table.
Error msg: "No unique index found for referenced field of the Primary table."
How do I fix it?
Do you want to edit the existing relationship? To create a new relationship, click No." displays. I have never seen this when linking non-ODBC tables.
For the last attempt, I started with a completely blank database, went into the Specs and changed all field Indexes to "No" (even though none specified 'unique') and still got the error. The text file is comma delimited with quotes around the text fields and field names in the first row, all of which is fine.
Regardless of whether or not I have Access create a primary keyfield, I still get the error.
Was there a "patch" in the last few weeks that messed up this functionality? It worked fine a few weeks ago with the same type of text files, just older data.
I'd try to open and save the file in Excel to see if that made a difference, but I have numbers with leading zeroes and Excel doesn't respect the quotes around the fields; at least Excel asa database is easily (and rightly) avoided because of such nonsense, but I want and need to use Access.
I have a db that I need to correct to ensure my tables will work with each other. Table 1 has Field Name [ServiceType] - Data Type [Text], Table 2 has Field Name [ServiceType] - Data Type [Number].
These two fields are the same data but are entered from two different forms that perform two entirely different jobs.
I want to change table 2 Data Type to "Text". I get an immediate error message that says I can't do this because there are relationships between the two tables and I need to delete this or these relationships before I can make the change.
When I click on the "Tools - Relationship" tab I get a screen that indeed has the relationship. I delete the line between the two tables close and save the change.
Then I try to make my change and the error message returns. I checked the relationship screen again and find that the change I made is ok.
What am I missing? Is there another path to the relationship screen I should be looking for such that I can make the relationship changes and therebye make the table changes?
It will allow me to create a relationship between the two fields in question, but if I try to enforce referential integrity, it crashes and won't do it.