Our newest round of Access bug fixes was released on October 27. 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’re on the current monthly channel build 2210, you should have these fixes. Make sure you are on Access Build # 16.0.15726.20174 or greater.
|
Bug Name
|
Issue Fixed
|
|
Cannot create a DAO field object for Date/Time Extended type
|
When using the DAO.TableDef.CreateField method to add a new field to a table definition, the method would fail with the error “Invalid field data type,” if the specified data type was 26 (which indicates Date/Time Extended)
|
|
Bug in Expression Builder in some languages
|
In the expression builder, terms such as ‘Form’ were being localized based on the UI language of the Office installation, which would cause expressions to fail to evaluate, since the expression service expects these terms to remain the same, regardless of language.
|
|
Error reported when using the Nz function
|
If the second argument to the Nz function specified the name of a field, then when the first argument to the Nz function evaluated to Null, the function would fail with the error “Invalid use of Null.”
|
Please continue to let us know if this is helpful and share any feedback you have.
