Error message when you use Access 2000: "The Microsoft Jet database engine cannot find the input table or query '<name>'" or "The record source '<name>' specified on this form or report does not exist" (208621)



The information in this article applies to:

  • Microsoft Access 2000

This article was previously published under Q208621
Moderate: Requires basic macro, coding, and interoperability skills.

For a Microsoft Access 2002 version of this article, see 287696.

SYMPTOMS

When you open or make a reference to a linked table in Microsoft Access, you may receive one of the following error messages:

Error message 1

The Microsoft Jet database engine cannot find the input table or query '<name>'. Make sure it exists and that its name is spelled correctly.

Error message 2

The record source '<name>' specified on this form or report does not exist.

Error message 3

Microsoft Access can't find the object '<name>.'

Error message 4

Run-time error '7874': Microsoft Access can't find the object '<name>.'

CAUSE

Microsoft Access could not find the linked table, or the external .mdb file does not exist anymore or is in a different location. This error also occurs when a deleted or renamed table is referenced on the Autolookup tab in Design view of a table.

RESOLUTION

To troubleshoot this situation, do the following:
  • Check to ensure that the table or query exists. If it does not exist, you must remove all references to it from your application. Often, the RecordSource property of a form or report contains a reference to an object whose name has changed or an object that has been deleted.
  • If the table of query exists, it is likely that there is a syntax or a spelling error in your reference to it. If so, correct the syntax or spelling in the reference.
  • When you try to open a linked table, the file containing the table isn't on the path that you specified when you linked it. If you have moved the file, you can use the Linked Table Manager to update the link information.

Modification Type:MajorLast Reviewed:6/20/2006
Keywords:kberrmsg kbprb kbusage KB208621