From time to time, I get the message
'Run-time error 3078
The Microsoft Access database engine cannot find the input table or query 'tblClaimsByPeriodSummarisedSource'. Make sure it exists and that its name is spelled correctly'
Things I've checked, after researching online:
1. It's a local table. No ODBC connection or a link to an external Access database is being lost.
2. It definitely does exist. If I have the Access Objects panel open when I run the code I can see it. I can also open it by double-clicking on it. In case it was some kind of refresh problem, I added a line to refresh the tabledefs for the db just before the line referencing the table. This made no difference.
3. It's spelled correctly. I even used 'rename' to copy the table name and overwrite the name in the code, just in case I was missing a typo. The fact that the code runs the majority of times I try also suggests to me that the table name can't be misspelled in the code.
4. This error happens at random times. I've found no pattern in terms of time of day, person using the database, etc. Somehow it seems to know when it will cause the most embarrassment (i.e. my manager needs to use it), but I think that's just a coincidence
Does anyone know of any reason why a db would sometimes act as if the table isn't present, when it is?
I don't know if it's relevant, but I'm using Access 2010.
'Run-time error 3078
The Microsoft Access database engine cannot find the input table or query 'tblClaimsByPeriodSummarisedSource'. Make sure it exists and that its name is spelled correctly'
Things I've checked, after researching online:
1. It's a local table. No ODBC connection or a link to an external Access database is being lost.
2. It definitely does exist. If I have the Access Objects panel open when I run the code I can see it. I can also open it by double-clicking on it. In case it was some kind of refresh problem, I added a line to refresh the tabledefs for the db just before the line referencing the table. This made no difference.
3. It's spelled correctly. I even used 'rename' to copy the table name and overwrite the name in the code, just in case I was missing a typo. The fact that the code runs the majority of times I try also suggests to me that the table name can't be misspelled in the code.
4. This error happens at random times. I've found no pattern in terms of time of day, person using the database, etc. Somehow it seems to know when it will cause the most embarrassment (i.e. my manager needs to use it), but I think that's just a coincidence

Does anyone know of any reason why a db would sometimes act as if the table isn't present, when it is?
I don't know if it's relevant, but I'm using Access 2010.