"not an index in this table" error
Thank you for taking the time to report an issue.
What's wrong... Please write below.
Should Itake off the index in the table or is there a way to redo the module to account for the index? It is a big table and want it to run as fast as possible when I run a query off it.
tblLoans.Index = "PrimaryKey"
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 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?
Every time I try to index, (I go in design view and set the "index" to yes with duplicates OK.
CANNOT OPEN DATABASE ITEM_NUMBER. It may not be a database that you application recognizes, or the file is corrupt.
Item_number is a field not a database. It just don't get it. I've tried to index other fields. same outcome.
With Windows 7, it seems that this practice leads to the following error when the file is imported to Access:
"The changes you requested to this table were not successful because they would create duplicate values in the index, the primary key, or relationship. Change the data in the field orfields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again."
I know that none of the fields of the destination table are indexed and there is no primary key. The table has not changed in between the windows conversion. In addition, I get the sameerror if I import into a new table.
My current work around is to open the .lis file in Excel and save it as text with no further modification to the file. When this is done, the file imports flawlessly. I would like to avoid this as the file is very large and it takes some time to open.
other than something related to the primary key or index (which again I do not have).
Error msg: "No unique index found for referenced field of the Primary table."
How do I fix it?
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
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.
The first table is "Cases" - primary index is CaseID, which is unique (of course).
The second table is called "Parties", and tracks the parties that were involved in the Cases - primary index is PartyID.
Now if that were the extent of it, I'd create a "juncture" table named "Cases_Parties" that housed CaseID and PartyID. There would be a one-to-many relationship from"Parties" to the juncture table "Cases_Parties", and a one-to-many from "Cases" to the juncture table "Cases_Parties".
So far, But the snag(s) is, a party can be either a plaintiff or a defendant in a Case. Where do I house the info that the party was either a plaintiff or a defendant in the case?
Also, a case can have multiple plaintiffs and/or multiple defendants? How do I handle a situation like that?