Access Problem

Anonymous
2016-12-19T20:33:30+00:00

The record Source

Lists all my choices in a combo box says they do not exist in the table but on the form they show. Added some new items wasn't in design view but it let me add them.  Now in every column I get this error.

Error

The record source

My listings";"Mylistings2";"mylistings3' specified on this form or report does not exist.

The name of the record source may be misspelled, the recordsource was deleted or renamed, or the recordsource exists in a different database. 

In the form or Report's design view or layout view, display the property sheet by clicking on the properties button, and then set the record source property to an existing table or query.

Did that but still get the error?

Help

Tried to go off a old backup but it still does it.  Would just like to use the backup and start from there as we haven't added much data since the backup.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. ScottGem 68,775 Reputation points Volunteer Moderator
    2016-12-19T21:28:44+00:00

    You need to get your terms right before we can provide a solution. 

    A Recordsource is the source of all values that a form can display. This value is either a tablename, queryname or a SQL statement. If it is a SQL statement (SELECT ...) then it has to be a valid statement. You can only set the Controlsource for controls on a form to fields that are listed in the Recordsource. A Controlsource is the field that a specific control is bound to.

    Not sure what you mean by listings. There are controls known as List controls. Among these are combobxes and listboxes. These 2 types of controls have Rowsources. A Rowsource specifies what values will be listed in the list control.

    So it does appear you are trying to set a Recordsource ("set the record source property to an existing table or query"). However, it also appears that you have controlsources, that are not in the Recordsource selected. That would generate the error message you are getting.

    If that is the case, then you probably need to create a query for your report, that joins multiple tables so that all the fields needed for the report are included in the Recordsource. On a form, however, you probably don't want the Recordsource to be multiple tables, but rather to use a mainform/subform to display data from multiple tables.

    0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-12-19T20:53:15+00:00

    The Record Source is to which field the form control is bound to.  I think you meant to edit the control's Row Source.  Is it possible you edited the wrong property?

    0 comments No comments
  2. Anonymous
    2016-12-20T12:55:34+00:00

    It is fixed there were some differences in the Row Source type that I changed and allow multiple values, column widths I did have a different correct table with combo boxed with different information but screen shot those properties and it works.  Thank you so much for all your help.  Have a great Holiday.

    Thank you,

    Cheryl Brumbly

    0 comments No comments
  3. Anonymous
    2016-12-20T12:56:54+00:00

    It is fixed there were some differences in the Row Source type that I changed and allow multiple values, column widths I did have a different correct table with combo boxed with different information but screen shot those properties and it works.  Thank you so much for all your help.  Have a great Holiday.

    Thank you,

    Cheryl Brumbly

    0 comments No comments
  4. ScottGem 68,775 Reputation points Volunteer Moderator
    2016-12-20T13:30:34+00:00

     and allow multiple values, 

    Be aware that using an MVF (multi-value field) will cause problems if you want to scale the database to SQL Server or other database engine. Also MVFs can be confusing to work with. I would recommend not using them and using the more traditional Junction table to model a many to many relationship.

    0 comments No comments