unknown row source being used for a field that is defined as text in a source table

[JosmithTwo]

I've been give an Access db that has been cut up from it's original. It has a table "Frog" that has a text field "Name", among others. I put the "Name" field as the 1st position in my query, when run it gives me an error message saying the record source 'SELECT [allFrogsNames].[ID], [allFrogsNames].[Name] FROM allFrogsNames ORDER BY [frog type];. I can see this in the row source of the query in Object definitions documentation but NOT in the query itself.


I have found that if I move the offending field so it is not in the first position of the query, I don't get the error.


Obviously there was a table (allFrogsNames) that was used to get the frog's name in the Frog table but it no longer exists. It might have been used to fill the Frog table with names.


Any idea as to how I can get access not to use the row source query?


Jim

[June7]

Not understanding. If allFrogsNames does not exist then field order should not matter and should still error.

Queries don't have RowSource - comboboxes, listboxes, graphs have RowSource.

Forms and reports have RecordSource.

If you want to provide db for analysis, follow instructions at bottom of my post.

[Micron]

I've read at least twice and can't see where you said what the error message is. Regardless, Name is a reserved word and is a poor name for anything you create. You imply that your query is based on a table, but if it's not, let us know. Maybe June7 knows off the top that it's OK, but I wouldn't have thought to ORDER BY a field that is not part of the SELECT statement - would have suspected an error, but if not, unreliable results.

[June7]

Field does not have to be included in SELECT to be used in WHERE or ORDER BY. Same result if field is in SELECT.

Possibly field is a Lookup type in table. Lookup field in table can be aggravating. Review https://access-programmers.co.uk/for...ghlight=zombie