What is your criteria for removal?
Why can't that just be added to a new query which is based from your original?

The Recordset has 5 fields and if three of these fields are the same the second and subsequent records are thrown away. The query is a UNION query, quite complex. I really need to evaluate each record against it's adjacent (sorted) record for duplicates in these three fields so VBA seems to be a logical choice. I have the VBA working fine except it throws the error when I do find a record which needs to be discarded and make an attempt to delete it. I'm about ready to create the temp table to just get through this issue and move on. It would just be elegant to just run through the Recordset and toss those which aren't wanted and then feed the report with the modified Recordset. I guess that would make it too easy :-)

Glenn could you add a field, called "DelFlag" for instance, and then update that field to true with your record set?
Then feed the report with the data where the DelFlag = False?

Are you permanently deleting the record from your db?  
I've found this helps in that case also.  First mark the records for deletion.  Then delete the records that are marked.  I've had issues deleting one at a time "on the fly" before and this method solved my problems.

Even that solution may not be of value to you.   Due to the complexity of your query.
See the video:  Not Updateable

In deciding whether to set this additional field to True or False, I might as well just perform the delete operation. I can't have dissimilar fields in the UNION so the "manipulation" of the results can best be addressed in VBA code, which is pretty simple with a couple of if's. The complexity of this is the result of tracking miles traveled to businesses or clients and combining that with distances traveled to FedEx and USPS, for instance. The business travel doesn't require shipping so it's in a "tblTransaction" table (for lack of a better word) and the shipping is in a tblShipping table linked to the "tblTransaction" table, but it's conditional in that the shipping is done from our office to a shipping station and not a client or agency shipping to us. We have to keep track of all routes that documents take throughout the process. Thanks for your contributions to this dilemma.

To answer your direct question, Scott, no we are not deleting any records from any database tables, simply reporting of the contents in a way that can be used for other reports (in this case, business travel for tax reporting purposes).

Another option that came to mind (even though I wouldn't know how to do this) is to skip records with have the same info in the three fields from being output in the report by filtering within the detailed section of the report itself (seems like a jury rigged implementation). I might experiment with something simple to validate this method. It would certainly educate me on how records are processed within this report event!!

Feed your Union Query into an Aggregate Query to remove the duplicates (Group By).

I ended up using a table and as I processed the records via VBA, saved off the one's I wanted to the table. I then fed the report from the table's record source. Using an aggregate query would be problematic since there is additional processing if records are "deemed" to be duplicates. By that I mean they aren't really duplicates in the purest sense, only certain fields match each other and even that some of those fields might have "FxE" or "FxG", but are considered "duplicates" since I only take one trip to FedEx whether I'm shipping a package via FxE or FxG (Ground). So the processing is a little more complex than just looking for pure duplicates. The solution works very well. I can deal with the fact that I can't delete the table within the VBA or when exiting the output form but I do delete the table when I start a new DB session.