Access export to rtf syntax error

New Contributor
I have Office 365 and when trying to export from Access to a Word doc (rtf) I receive the following error:
"Microsoft Access can't complete the Output operation"
The Visual Basic code you entered contains a syntax error or the Output procedures are not available

Please note that error pops up in a dialog box when I try to import to a .rtf file.
Using Windows 10 Home
HP Spectre x360
64 bit
12 Replies
Make sure your code fully compiles before you run the code again.
If it still fails, add error handling and pinpoint the exact line where the code fails.
Then post the code & the full error message including the error number
Appreciate your reply and time but this is what frustrates me with Microsoft Customer Service. They directed me to the forum to help resolve my issue but I am my expertise is not in the arena. I actually have zero idea what you were suggesting.

And I am afraid not being able to discuss with technically experienced individuals is going to keep me from resolving an issue that I believe Microsoft Customer Service should have been able to diagnose.

Thanks again, tho.

OK so take one step at a time and hopefully we'll be able to help you solve this issue.
1. Do you know how to compile your code?
2. Do you understand how to add error handling or how to step through code to see where it breaks?

Please post the code which causes your error
Access rtf is but a subset of a real rtf file. so &nbsp (non breaking space) is not on it's subset.
you should Directly use Word automation to Open the .rtf file.
Honestly, no to both.



Access is unlike other Office applications in that it REQUIRES a minimum level of knowledge to create viable relational database applications. And that means we all have to invest time and effort in acquiring that minimum level of knowledge. 

No amount of technical support is going to replace it, either.

So, you have responded "no" to the questions about compiling code and about error handling.


In order to get the help you need, the next step is going to be sharing the code where this failure appears. ALL of that code, not just the single line that appears to be failing.

Thanks for providing sufficient detail to allow us to help.


I feel your pain, Bradly.  I just started having the same problem. I have a report that I've been using for over ten years.  I right click on the report, select Export, then Word RTF file.  There is no code created by me.  This is standard MS code.  There's nothing to compile or add error handling to.  I choose my file name and destination then click OK.  I get this error: 


This routine is repeated from more than one workstation and more than one database.  To be clear, this is a new error as of Monday, August 1st, 2022 and I have performed this routine hundreds of time over multiple years.  It's puzzling and frustrating to get an error for a standard routine.  I'm going to reload Access to see if that clears the problem.  

I have the same problem (Export a Report in .rtf format), but it works for exporting in .pdf format.
Something has changed. I'm on Office 2013 and just moved to Win11 last month.
Has some function become obsolete?



It's looking likely that this is a new bug as of last week. A number of reports are saying several types of exports no longer work.


This seems to be related:

In my mind companies should not be on Current Channel.


10 days ago, I didn't have the update for MS 365 installed yet. So I was able to export the data to a list and this list to Word RTF to a colleague. A colleague could not do this because he already had this update installed. In the meantime, the SW-center also installed this same update on my PC. Now I can't export the created list from the same Acess database, except to PDF. The PDF format does not suit me due to the further processing of the list in Word.

In the forum below on the given links, I also did not find the right solution. Even restoring my PC to pre-August 4th doesn't fix this export for me.

Since I have the ability to use Access 2003 in a virtual environment, I'll do thise export there for now. But this is not a solution.

It seems that this error is already known. The date of the first records on this chat is from December 6, 2021. Has the error happened again? Has it been fixed once in the meantime and forgotten about with new upgrades?