Append Query multiples appending. HELP

[AlliCrader]

I am trying to create an append query that will only append data based on a like criteria and if one of my fields is not in the table(which they should not be in there to begin with). The problem is, it is appending the records multiple times and I don't know how to fix this. Please help.

[JoeM]

I have a feeling that the issue is with the underlying data source (RMA).
Try changing your Append Query to a Select Query and play around with it until you have the correct number of records displaying that should be added to the Table.

[Micron]

it is appending the records multiple times.

What does this mean, exactly? That each time you run it, it appends records that are already there, or in one execution it adds multiple identical records? I don't get this either

if one of my fields is not in the table(which they should not be in there to begin with)

If the field is not there, how can your query add data to it? I think you mean if a table field doesn't have values in it that your query is trying to append, then it should append, otherwise, it should not.

What is RMA - a table, or query?

[ssanfu]

FYI: you have spaces and special characters in your field names.

Some suggestions:
Use only letters and numbers (exception is the underscore) for object names.
Do not use spaces, punctuation or special characters in object names.
Do not use look up FIELDS, multi-value fields or calculated fields in tables.
Do not begin object names with a number.
------------------
Bad field name: "RMA #" (has the hash mark and a space)
Good/better field names: "RMANum", "RMA_Num", "RMA_Number"


(The hash mark (#) in Access is a date delimiter)

[John_G]

Your query is going to copy all matching records each time you run it. This will result in duplication in the destination table unless you delete the records after copying them. Your criteria says "MOVE TO EXPIRED", but your query does not "move" records - it only copies them. You need a second, Delete query which you would run AFTER the first one.

[Micron]

Table fields that don't allow duplicates can also prevent duplicate records. Use the .Execute method to run the query to avoid warning messages. A gram of prevention is worth a kilo of cure.

That's if the duplicates are in the same table. No answer to that yet?