Re: Bizarre and frustrating! Phantom ambiguous field reference in a query
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Wed, 1 Jun 2005 00:04:39 +0800
If this is Access 2000 or later, the first thing to check is that you have
unchecked the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html
After that, compact the database.
You could also switch the query to SQL View, copy the (correct) query
statement to clipboard, delete the query, create a new query, switch it to
SQL View, and paste in the SQL statement. That should completely stop Access
from confusing the objects based on the Name AutoCorrect info.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Bill Reed via AccessMonster.com" <forum@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:b688903348144af5a1e39325da132935@xxxxxxxxxxxxxxxxxxxx
> Just when you think you've seen everything.
>
> I have a query that's been working ok as the datasource for a form. Now I
> want to filter that query using a "Where" clause string that's
> concatenated when the db opens. I added a query to the form's datasource
> query to provide the necessary fields for the "Where" clause to filter on,
> and now a field, "Status", that heretofore never gave me a problem, is
> displaying as "Status.Status" in the query result field heading, as though
> there were another table/query in the grid that had the same field name. I
> can absolutely assure you that is not the case. The only instance of that
> field name is in the table "Status". (I'm stuck with the names of these
> tables which were created by a novice without regard to possible
> duplication of object names (or, in this case, field names identical to
> parent table names)). But I am completely baffled as to why the original
> query, which also only had one field named "Status" in the grid, had no
> difficulty with the field name being the same as the parent table name.
>
> This nonsense has repercussions throughout the db.
>
> Has anyone seen anything like this before?
>
> Thanks
>
> --
> Message posted via http://www.accessmonster.com
.
- Follow-Ups:
- Re: Bizarre and frustrating! Phantom ambiguous field reference in a query
- From: Bill Reed via AccessMonster.com
- Re: Bizarre and frustrating! Phantom ambiguous field reference in a query
- References:
- Bizarre and frustrating! Phantom ambiguous field reference in a query
- From: Bill Reed via AccessMonster.com
- Bizarre and frustrating! Phantom ambiguous field reference in a query
- Prev by Date: Bizarre and frustrating! Phantom ambiguous field reference in a query
- Next by Date: Things happening at the same time
- Previous by thread: Bizarre and frustrating! Phantom ambiguous field reference in a query
- Next by thread: Re: Bizarre and frustrating! Phantom ambiguous field reference in a query
- Index(es):
Relevant Pages
|
|