Forum Discussion
Access export to rtf syntax error
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.
Cindy_Sweeny
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: https://support.microsoft.com/en-us/topic/error-when-trying-to-use-docmd-transfertext-with-an-export-specification-b8ddf34a-da94-48bb-9d3a-66743f355893
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?
