"FieldName" is not an index in this table. Error 3800
Option Compare Database Public Function VerifyAcct(AcctNum As String) Dim dbDatabase As Database Dim rsAcctNumber As Recordset Set dbDatabase = CurrentDb Set rsAcctNumber = dbDatabase.OpenRecordset("CAM_Portfolio_Query", dbOpenTable) With rsAcctNumber
.Index = "Account-Number"
.Seek "=", AcctNum
If .NoMatch = True Then
End If End With
It is giving me Runtime 3800, "FieldName" is not an index in this table.
In the table CAM_Portfolio_Query, I set the [Account-Number] field to be both the key and indexed, with no duplicates allowed.
Yet I still get this 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?
If I use Format([TableName.FieldName],"v0") in a query, I get the results I want: v1, v2, v3, etc. But if I use Format([TableName.FieldName],"s0"), I get this: 01, 02, 03, etc. How do I get s1, s2, s3, etc. instead
Then sometimes (but not everytime) I get a message that says "The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted.
Deleting the VBA project removes code from modules, forms and reports. Your should back up your database before attempting to open the database anddelete the VBA project."