Folks ... this is an answer AND a question.
I just spent an hour or so toying with what I believe is a bug in Access 2010 - and figured I'd share my experience/findings with everybody for 2 reasons. First - so you can avoid my problems; and, second - in case somebody has a more clever workaround than what I've found.
To give full credit the bug/workaround I "found" are located at this URL - although I'll say it took me a while to find this URL.
http://social.technet.microsoft.com/Forums/en/offi ce2010/thread/d9d2abf3-859f-4920-8964-900b9f5b6347
Here's what I specifically did - and what I saw:
I created a query in Access 2010
I right-clicked the query name and chose to export to a text file
I created an export file spec for my query and saved the spec as "SymbolsOnly". The purpose of the spec for me is that I didn't want quotes surrounding the text being exported.
I completed the export - it ran fine
I then created a Macro tied to a command button that would run the export for a user.
I used the ImportExportText Macro Action.
I chose the File Spec from the drop-down list that Access provides (so there were no spelling issues involved).
I tested the export - and got the error message "The Text File specification '1' does not exist. You cannot import, export, or link using the specification."
I went back and re-tested doing this manually by right-clicking the Query but this time loading the saved spec and exporting - it worked fine! So - I know it's not corruption.
I re-tested via the button - error.
I created a duplicate spec, modified my macro by selecting the duplicate spec from the drop-down list (again, no spelling errors are possible this way) and tested. This time the error was for Text File specification '2'. Really weird!!!!!
I started digging - and found the link above. The author said they tried naming their file spec "1." I deleted all my specs and created the spec from scratch - naming it "1." I tested it manually - it worked - then I tested via the command button - it worked.
How horrible is that?
So - my new export spec is intuitively named "1." That will help me later on when troubleshooting this app.
Hopefully this info is found by somebody having the same issue I had - and you get your answer quicker than it took me. As it is - if anybody wishes to reply to this thread with insight as to why this happens in Access 2010 ... or alternative solutions that may allow for more intuitively-named specifications ... I'm all ears.