I do not see why renaming a query would cause it to fail. Are you using
this query in another query? And that query is the one that is failing? If
so, that would explain the problem. What you might do in such an instance is
rename the qStreet query, then open up the query that depends on it in SQL
view. Where it says "...FROM qStreet...", change to "...FROM qStreetNew AS
qStreet...". Then go into design view. Right-click on the "qStreet" item in
the top section and choose Properties. Change the Alias to qStreetNew and
press <Enter>. Try running it to see if it now works correctly. If that
does not solve the problem, post the SQL of the queries involved and their
names.
Clifford Bass
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-queries/201001/1
I have seen this happen when after you rename the query you don't check the
OrderBy field. While the query has been renamed the OrderBy still says
Order By: qStreet.field1. Fix that by either putting in the correct name of
the query of simply deleting what is on the OrderBy line.
--
Gina Whipp
2010 Microsoft MVP (Access)
"I feel I have been denied critical, need to know, information!" - Tremors
II
http://www.regina-whipp.com/index_files/TipList.htm
"finster26" <fins...@discussions.microsoft.com> wrote in message
news:1E3B299B-865C-4240...@microsoft.com...