Please use # icon on toolbar when posting code snippets.
Cross Posting: https://www.excelguru.ca/content.php?184
Debugging Access: https://www.youtube.com/results?sear...bug+access+vba
Just to add that the problems with exporting to HTML with formatting are wider than it first appeared.
I have done some extensive testing and ALSO found errors with the actual HTML output:
a) errors with additional characters being added at the end of the first field of the first record
b) a nonsensical field being added to the output of an exported form containing an unbound checkbox
I've reported the issues to the Access team who have confirmed my findings and the causes are being investigated
My apologies for taking so long to reply, but I didn't know where to look for the information you were asking for.
The build info listed under "About Access" is Microsoft Access for Microsoft 365 MSO (Version 2508 Build 16.0.19127.20082) 32-bit.
Please note that this is a different build than when I originally posted, as I forced an update to the latest version. The update did not resolve the issue.
My Windows Specification is Windows 10 Pro, Version 22H2, OS Build 19045.6216.
Thanks but things have moved on since I asked the question.
A reminder to provide the version and build info to the right of the About Access button and not that displayed at the top of a separate dialog box when the button is clicked
The encoding seems to be related to some essential compliance work done in recent months.
However there are wider issues with the HTML output as well which the Access team are investigating.
I’m going to write this up as a web article with additional examples in the next few days.
Its too soon to say how or when it will be dealt with
In the meantime. I suggest you either disable the export with formatting option in the wizard or do the export using code (DoCmd.TransferText)
Just a quick update to say I've just published a new article outlining the issues with the Export to HTML wizard using the Export with formatting and layout option.
The issues go beyond the additional encoding of numerical data as there are also data changes in the HTML output for both queries and some forms (those with unbound checkboxes)
See Export Objects to HTML Encoding Issues
Thanks to @kdpoter for first raising the encoding issue and to @welshgasman for prompting me to investigate it properly.
I will update this thread when I get any news about a fix from the Access team
Thanks Colin.
Please use # icon on toolbar when posting code snippets.
Cross Posting: https://www.excelguru.ca/content.php?184
Debugging Access: https://www.youtube.com/results?sear...bug+access+vba
That update appears to have broken my conditional formatting with an expression and comparing against a TempVar.![]()
Please use # icon on toolbar when posting code snippets.
Cross Posting: https://www.excelguru.ca/content.php?184
Debugging Access: https://www.youtube.com/results?sear...bug+access+vba
UPDATE:
The Export To HTML with formatting issues have been fixed in the latest Beta channel update to version 2509 build 19230.20002 released on 2 Sept.
The fix should roll out to other channels in the near future.
The fixed version no longer encodes any of the data and the resulting data errors in the output have also been eliminated.
![]()