This post has been republished via RSS; it originally appeared at: Access Blog articles.
Our newest round of Access bug fixes was released on April 25, 2023. In this blog post, we are highlighting 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 build 2304, you should have these fixes. Make sure you are on Access Build # 16.0.16327.20214 or greater.
|
Bug Name |
Issue Fixed |
|
Some date filters do not work when there are Null values in the date column |
When filtering on a date column using the column filter menu (e.g., right-click on a Date column, and click Date Filter/Tomorrow), if there are Null values in the column, you would receive the error “Data type mismatch in criteria expression.” This is fixed to now exclude the Null values from the result with no error. |
|
When linking to a SQL Server table with a bigint column, Access does not prompt to enable linking as a Large Number |
Large Number is the Access type analogous to SQL Server’s bigint data type. If support for linking to bigints as a Large Number column is not enabled, then Access will treat the column in the linked table as a string. When linking to a table with a bigint column, Access will now prompt to ask if you want to enable support for linking to the bigint column as a Large Number. |