Access Releases 4 Issue Fixes in Version 2212 (Released January 4, 2023)

[Guest lindalu-MSFT]

Our newest round of Access bug fixes was released on January 4th. 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’re on the current monthly channel version 2212, you should have these fixes. Make sure you are on Access Build # 16.0.15928.20198 or greater.

 

 

 

Bug Name	Issue Fixed
When exporting to Dataverse, and filtering the list of available sites, Access may export to the wrong site	When exporting to Dataverse, there is a list of available Dataverse sites to export to, and you may filter this list by typing in a search term. If you select the 3rd item in the list of sites, Access will always export to the 3rd item in the original list, even though that may no longer be the same as the 3rd item in the list when it is filtered. This fix ensures that Access will export to the selected site, whether the list is filtered or not.
Setting the Horizontal Anchor property to Right may change the property value for controls to the left in a layout	The Horizontal Anchor property determines whether a control in a layout is moved to the left, right, or attempts to stretch across a span (when the property is set to Both). When setting the Horizontal property to Right, it implies that controls in line with or to the right of the target control should also try to align to the right, so the property is updated for those controls. However, setting this property should not impact controls to the left of the target control in the layout. This fix corrects the behavior so that only controls in line with, or to the right of the target control in the layout are affected.
Query design does not allow specifying Is Null as the criteria for a Date/Time Extended field	Specifying the string Is Null as the criteria for a column in the query designer should result in a query that finds records where the column has no value. However, when Is Null is entered as the criteria for a Date/Time Extended field, the query designer adds quotes to the string, resulting in "Is Null" being specified as the criteria value. This fix prevents the Is Null expression from being quoted incorrectly for Date/Time Extended fields so that the query will correctly find rows with no values in the column.
When specifying a Date/Time literal as the criteria for a Date/Time Extended field, an error occurs “Data type mismatch in criteria expression”	When specifying the criteria for a Date/Time Extended field in the Query designer, you can use a string value to specify the criteria, but if you use a Date/Time literal (a Date/Time value surrounded by ‘#’ characters) an error will occur. Although Date/Time literals do not support the full range of values supported by a Date/Time Extended column, it should work properly for values in the range supported. This fix enabled Date/Time literals to be used as criteria for a Date/Time Extended column without error.

 

 

 

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

 

Continue reading...