Append Query Hangs

I see two real world solutions here.  I am making two assumptions.  One the table dbo_V_ATIExcizeExport is a linked sql table.  Two you can create tables and views within this server.

1. Pull dbo_V_ATIExcizeExport into the access database to leverage access slight gain in speed for working with both tables locally to the database instead of linked.  Then insert into a 3rd temp table... i would call it tblTracking_Tmp where it stores only the new records then store that result in tblTracking without the where clause so that access doesnt have to iterate the entire table prior to filtering on the where clause.  You really dont "Win" in this situation because you are still iterating the entire dataset with the where clause within access. 
2. Create a tmp table in the linked sql database with mirroring of the design to dbo_V_ATIExcizeExport.  upload tblTracking into a tmp SQL table.  create a view that performs the filter server side.  link to that view and insert that view into your local tblTracking table.
    

necrit
Both tables are local, dbo_V_ATIExcizeExport is an import from a linked view, tblTracking is the table that is update from  dbo_V_ATIExcizeExport local table tblTracking will have additional data added to it I need to keep that tables data intact I just want to append the records from   dbo_V_ATIExcizeExport that do not reside in tblTracking

Then instead of importing dbo_v_atiexcizeexport why not upload the tbltracking to the server and have hte sql server perform the outjoin server side and then pull in only the delta of new records from a custom view that will be then just dumped into the tblTracking?

Let me explain the function of the database. Because we are an Importer we are required to pay excise tax on any imported item we sell, this database keeps track of the paid taxes.  dbo_V_ATIExcizeExport is a table that I flush and fill from a view comprised of several tables on our SQL Server it contains customer and item information which changes constantly, tblTracking has the same schema but it is where the date and amount of the tax is recorded, therefore can not be flushed. All I want to do is append the records from dbo_V_ATIExcizeExport that do not exist in tblTracking. That is the reason I have the tables local assuming the append would be fast,(Wrong). I used the invoice number as the query point. The invoice number is unique in that only one invoice number is assigned per order but if the order has multiple lines the invoice number is on each line therefore I cant use Distinct or make it a PK with no Dups. Is it possible to use WHERE NOT EXISTS as opposed to WHERE (((Exists (select Invoice_No from tblTracking where tblTracking.Invoice_No =dbo_V_ATIExcizeExport.Invoice_No ))=False));

Invoice_No      ITEMNMBR      SERLTNUM
111435      2224AK47      A342915
111435      2224AK47      A342913
111435      2224AK47      A342912
111435      2224AK47      A342911
111435      2224AK47      A342910

Does anyone have a suggestion to my dilemma

Does it work with 10 records tables?

<pre id="codeSnippet425126" class="prettyprint">First make a new table (call it cpyTracking) which holds ONLY the Invoice_No values from tblTracking
then:

INSERT INTO tblTracking ( CUSTNAME, CUSTNMBR, Freight_Amt, SHIPPING_MTHD, Invoice_No, Invoice_Date, ITEMNMBR, SERLTNUM, PRODUCT_TYPE, UNIT_PRICE, DATE_PAID, AMT_PAID, VENDORID, VENDNAME, ITEMDESC )
SELECT dbo_V_ATIExcizeExport.CUSTNAME, dbo_V_ATIExcizeExport.CUSTNMBR, dbo_V_ATIExcizeExport.Freight_Amt, dbo_V_ATIExcizeExport.SHIPPING_MTHD, dbo_V_ATIExcizeExport.Invoice_No, dbo_V_ATIExcizeExport.Invoice_Date, dbo_V_ATIExcizeExport.ITEMNMBR, dbo_V_ATIExcizeExport.SERLTNUM, dbo_V_ATIExcizeExport.PRODUCT_TYPE, dbo_V_ATIExcizeExport.UNIT_PRICE, dbo_V_ATIExcizeExport.DATE_PAID, dbo_V_ATIExcizeExport.AMT_PAID, dbo_V_ATIExcizeExport.VENDORID, dbo_V_ATIExcizeExport.VENDNAME, dbo_V_ATIExcizeExport.ITEMDESC
FROM dbo_V_ATIExcizeExport
WHERE Invoice_No not in (Select Invoice_No from cpyTracking)

That should be MUCH faster.

AW
</pre>

Sorry I haven't responded sooner but  I have been busy for the last few days. I will try the suggested fixes and report back.