Append query with an Inner Join to Destination Table Not working

[k2harrell]

I have an issue that popped up in the last couple weeks. Both work and home
using Office Pro 2003 SP3, Access 2003. Before around 3/20 I was able to
select an append query with the destination table included as part of the
query (inner join, with 'is null' on the primary keys). I have written them
the same way for 12+ years, and never seen this occur, where the destination
table (table I'm appending the missing records to) is not showing up in the
list of tables to append to.

I haven't tried to add the destination table manually in SQL view with
INSERT yet (which might work), but for whatever reason it is not showing up
in the list of tables when I select 'Append' query while in the grid view.

Anyone else seeing this? I'm not seeing this problem on my home computer
version.

 

[KARL DEWEY]

What about if you change it to an append query with the destination table
included as part of the query (LEFT JOIN, with 'is null' on the primary keys)?

 

[k2harrell]

I'm sorry Karl. I typed wrong. It is a left join.

What I'm seeing is that previously I could write the query I wanted in grid
view (basic select query), just to verify that the results of my query using
the join and null records appeared correct. I always check/verify the raw
data first to ensure the query is written correctly. Check now, save on
kleenex and tylenol!

Then if all looks correct, I just change it from a Select to an Append
query, and click the destination table from the drop-down list, which is the
table listed in the left join.

For whatever reason, the ability to do it in this order has 'gone away' in
the last few weeks. I can still do it in this order on my home PC, but not on
my work PC. Our in-house support staff at work is also looking at this, but
was thinking someone else in the 'office' community may be seeing it too, and
either not realizing that something is very different, or knows what caused
it.

What I have to do now is first create a non-joined Append query, without the
destination table included, then I can add the destination table and joins
with the null values on the primary keys in the destination table.

Basically, I have to create it in the grid using the same order in which you
would write it out manually in SQL. (insert into xxxx, then the from xxxxx,
join xxx and is null xxxxx statements.)

It still works (technically), but has always intutively written out to SQL
in the correct order without me having to do it in a particular order in the
grid view.

Hope that helps better explain the issue I'm seeing. I love workarounds when
they work, but also like to know 'why', 'when' and 'where' when something
appears to have changed for no apparent reason. Any help, advice or just
general comments are welcome and appreciated! \k2h