Blog Post

Access Blog
3 MIN READ

Access Releases 14 Issue Fixes in Version 2305 (Released June 1st, 2023)

lindalu-MSFT's avatar
lindalu-MSFT
Icon for Microsoft rankMicrosoft
Jun 06, 2023

If you see a bug that impacts you, and if you're on the current monthly channel build 2305, you should have these fixes. Make sure you're on Access Build # 16.0.16501.20196 or greater. 

 

Bug Name 

Issue Fixed  

Cannot use a link to a table in an Access database with 20-character password. 

The maximum length for a password on an encrypted database is 20 characters. However, if you use a 20-character password and create a link to a table in the database, you'll receive the error message “Not a valid password” when trying to use the link.  

When a control in a report has Can Grow or Can Shrink set to Yes, and uses conditional formatting, it may not correctly size the control. 

The size of the control was determined before conditional formatting applies, so if conditional formatting changed the size of the text (e.g., by applying Bold formatting), then the size of the control might not be appropriate after conditional formatting applies. 

The Result Type dropdown for a calculated column in a table does not show "Large Number." 

When you create a calculated column in a table, you can set the Result Type property of the column to determine how the column should be treated. However, the dropdown was incorrectly displaying ‘19’, rather than "Large Number." 

Reserved error (-7747) when trying to link to SQL Server table with a spatial index on a geography column.

You can now link to a SQL Server table with a geography column that has a spatial index. 

"#Deleted" displayed in table when linked to a SQL table with a geography column.

When linking to a SQL Server table with a geography column, Access no longer displays "#Deleted" for data in the table.

When "Allow Special Keys" option is off, breakpoints in VBA code do not work.

When the Allow Special Keys option is off, it correctly disabled the use of CTRL Break to trigger a break in running VBA code, but it was also preventing explicit breakpoints from being hit in code. Breakpoints set in code will now function properly. 

Error 3048 "Cannot open anymore databases" when exporting many reports to PDF.

A resource leak occurred when exporting/printing some reports, which could eventually lead to an error message when the resource was exhausted. The leak will no longer occur. 

Closing a report in print preview may cause Access to terminate unexpectedly.

This would happen with a particular combination of elements, including a subreport, a combo box, and conditional formatting. These elements will no longer cause Access to terminate when the report closes. 

Tables disappearing in Relationship window when selected and a table is saved in design view.

When the Database Relationships window was open and there were selected tables in the window, and then a table was saved from table design, all selected tables would be removed from the Relationships window. Saving tables will no longer remove tables from the Relationships window. 

DAO DataTypeEnum enumeration does not include a value for Date/Time Extended.

The enumeration now includes the value dbDateTimeExtended (26). 

When using the Zoom builder for the first time on a system with metric settings, the font is too small to be legible.

The font size will now default to 11pt the first time the Zoom Builder first opens on both U.S. and metric settings. 

Error calling Query/Table refresh multiple times from Excel workbook to Access database.

When an Excel workbook has a data connection to an Access database, refreshing the connection would leak resources. Eventually this would lead to an error when trying to refresh the connection. The leak will no longer occur. 

Document tabs don't meet accessibility contrast requirements. 

The contrast between the text color and background color of the document tabs now provides good legibility in all Office themes. 

DoCmd.OutputTo acFormatXLSX doesn't work. 

When using the DoCmd.OutputTo command with a report (using ObjectType = acOutputReport), and specifying acFormatXLSX as the output format, the report will now successfully export to an .xlsx file. 

 

Please continue to let us know if this is helpful and share any feedback you have.  

 

Updated Jun 06, 2023
Version 2.0

27 Comments

  • Chris_Jones2023's avatar
    Chris_Jones2023
    Copper Contributor

    To go back a few office versions just run this from CMD and everything works fine again. I've just put it in our login script across the company until a better version comes out.

     

    "c:\program files\common files\microsoft shared\clicktorun\officec2rclient.exe" /changesetting channel=broad
    "c:\program files\common files\microsoft shared\clicktorun\officec2rclient.exe" /update user

  • Chris_Jones2023's avatar
    Chris_Jones2023
    Copper Contributor

    Shane, quick update is that opening the database without anything loading does let me open a blank test report not connected to any tables in design mode however after doing that no obects of any type will open. And the reverse is the case that if I open the database and let everything run then it's ok but won't let me open reports?

  • Chris_Jones2023's avatar
    Chris_Jones2023
    Copper Contributor

    Thanks Shane, I can confirm that I can't even create a blank report without any tables connected once the database has opened. The tables I link too are a combination of local & SQL with an handful of ODBC links to Foxpro tables that are not accessed at load. I have also realised that despite the main dashboard being loaded, basic queries are failing due to insuffienct memory so I am going to step through each item that loads when the database is opening to isolate what is causing the insufficient memory issue. I suspect that a limit for loading a certain amount of records from a certain type of source has decreased dramatically to the point I cannot use the database once it's loaded

  • Hi Chris,

     

    We do have some reports, but don't have a reproducible case yet. Can you confirm that you can't even create a new blank report?  Or is it failing to create an auto-report where you are binding the report to an existing table?

     

    Are the tables you are using for the reports links to SQL Server tables?

     

    Shane

  • Chris_Jones2023's avatar
    Chris_Jones2023
    Copper Contributor

    Once I had been updated to this version of Office I cannot run or open reports in design view, print preview or even create a blank report without access stating that there isn't enough memory to perform this operation? I have attempted, without results, to perform the same report actions on a 1 year old backup of the front end database, decompiled and recompiled it, checked for corruption of the reports or VBA, reinstalled office and used a seperate PC with the same copy of office. Only the PC's with a previous version of Office can work correctly. The only way I can do anything with reports is if I hold down the shift key on open to disable any queries running on open. Only option I currently have is to disable office updates across the whole company

     

    Does anyone have an ideas or can replicate this issue?

    Best regards,

    Chris Jones, MS Access Developer

  • loufab's avatar
    loufab
    Copper Contributor

    Merci Linda.
    Oui c'est utile de diffuser les corrections.

    Car certains pensent à tort que MS Access est un produit mort ou en fin de vie.

    Cordialement,