Blog Post

Access Blog
2 MIN READ

Access Releases 9 Issue Fixes in Version 2312 (Released January 4th, 2024)

lindalu-MSFT's avatar
lindalu-MSFT
Icon for Microsoft rankMicrosoft
Jan 20, 2024

Our newest round of Access bug fixes was released on January 4th, 2024. In this blog post, we highlight some of the fixed issues that our Access engineers released in the current monthly channel.  

 

If you see a bug that impacts you, and if you are on the current monthly channel Version 2312, you should have these fixes. Make sure you are on Access Build # 16.0.17126.20126 or greater. 

 

Bug Name 

Issue Fixed  

No list of font sizes when Aptos font is selected 

Aptos is the default font for controls in a new database using the recently updated ‘Office Theme,’ but the font size drop down was not displaying a list of font sizes (although you could manually type in a font size). 

When a query was open in datasheet or design view, the context menu command to open in SQL View in the navigation pane would not switch the open query to SQL View 

This command on the context menu was recently added to allow opening a query directly into SQL view. However, to be consistent with other commands, it now switches the mode of a query that is already open to SQL view. 

#Error when using DateDiff with one Date/Time column and one Date/Time Extended column 

The DateDiff function was working correctly if both arguments were of type Date/Time, or both arguments were of type Date/Time Extended but would fail to evaluate with one argument of each type. 

The updated linked table manager no longer shows the name of the DSN used for a linked table 

The old, linked table manager displayed this information. The new linked table manager now also displays it. 

Access may terminate unexpectedly when running a macro after editing it 

In some cases, after adding/removing/moving macro actions in the macro designer, then attempting to run the macro, Access would terminate unexpectedly. This no longer occurs. 

F1 does not display the correct help page when used on some properties/methods of the Field2 object in the VBA IDE 

F1 now directs to the appropriate help page for the following properties/methods: 
CreateProperty, Expression, IsComplex, Name, Required, SourceTable, Type, ValidationRule, ValidationText, and Value. 

Some valid values for the DBEngine.SetOption method have no defined constant 

The following constants were added: 

dbPagesLockedToTableLock, dbPasswordEncryptionProvider, dbPasswordEncryptionAlgorithm, dbPasswordEncryptionKeyLength 

Subform control does not support LabelName property 

The LabelName property was shown in the property sheet for every other control that supported child labels and is now present for subform controls as well. 

Auto expand in combo boxes doesn't work for list items >100 index 

In some cases, autocomplete did not work for items in a dropdown list when there were more than 100 items in the list. This issue has been resolved. 

 

 

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

Published Jan 20, 2024
Version 1.0
  • Marcelodavid's avatar
    Marcelodavid
    Copper Contributor

    Good fixes!

    In the MySysObjects system table, in the Connect column, the passwords of linked databases are exposed. I believe this is a privacy and security flaw. Is there any plan to no longer expose the password?

  • JCappio's avatar
    JCappio
    Copper Contributor

    We have an environment that is using O365 32-bit across the board for ancient Access versioning(Yay!). The latest patch seems to have messed us up. We are seeing issues when opening MDE files:

    Working version:

    Not Working version:

    Any ideas would be greatly appreciated.

     

    Thanks,

    Jim

     

  • HeinziAT's avatar
    HeinziAT
    Brass Contributor

    According to our tests, the Feb 2024 security updates introduced some performance issue when loading large recordsets with DAO's OpenRecordset, but only in the Monthly Enterprise Channel (17126.20190) - Current Channel and Semi-Annual are fine.

     

    Are you already aware of this issue or do you want me to prepare a minimal repo example?

  • PhilS's avatar
    PhilS
    Brass Contributor

    The issue with "linked table manager no longer shows the name of the DSN" still persists with File DSNs.

    When linking a table using a File DSN this results in a DSN-less link where all information from the DSN is included in the Connect property of the linked table.

    This makes some sense, as File DSNs are hard to distribute for a wider user base. However, the user could have created the DSN-less link themself but they explicitly choose a File DSN. This choice should be honored and persisted in the Connect prroperty.

    (Applies to: Microsoft® Access® for Microsoft 365 MSO (Version 2312 Build 16.0.17126.20132) 32-bit)