UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Office Update Bug For Decimal Fields    
 
   
jleach
post Jul 1 2020, 04:55 AM
Post#1


UtterAccess Administrator
Posts: 10,583
Joined: 7-December 09
From: St. Augustine, FL


An FYI, from the Access Team's Ebo Quansah:

QUOTE
Very soon, we will ship a new data type, known as Date & Time Extended, which enhances syntax compatibility with SQL while increasing accuracy & level of detail in date & time records.

While the feature is not yet enabled in Current Channel builds, most of the code for the feature is in the product in an inactive state. Nonetheless, we are aware of a problem that currently exists with this new code. As of today, if you are on version 2005, build 12827.20010 or greater, and you manipulate Decimal fields (Access DataType=Number/FieldSize=Decimal, or SQL DataType=Decimal) using DAO (Data Access Objects), you might have identified your app crashing. If you hover a variable with the type in VBA code, you may see that the field is not being displayed properly; either reading as ‘?????’ or giving a Type Mismatch error, or Access may crash.

We are very sorry for the inconvenience this causes in your Access app. The Access team is working on resolving this issue as soon as possible, and we will report back to you once this error has been fixed. In the interim, we’d recommend for you to roll back to a previous version (https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic), or switch to a slower channel (e.g Monthly Enterprise Channel, or SemiAnnual Channel), until the issue is fixed in Current Channel. The issue only impacts Decimal types so if avoiding DAO code that manipulates Decimal types is possible, we’d advise this as a short term solution.

Thank you,

Ebo Quansah


As per usual, Daniel has collection some information and references here: https://www.devhut.net/2020/06/08/access-ve...using-problems/

And, a fix/workaround posted by MS here: https://support.microsoft.com/en-us/office/...en-us&ad=us

As of 6/24:

QUOTE
This is now fixed in all affected channels.

For Current Channel, version 2005, the issue is fixed in build 16.0.12827.20470. You may need to force a manual update to get the new version.

For Current Channel (Preview), version 2006, the issue is fixed in build 16.0.13001.20198.

--------------------
Jack D. Leach
Founder & CEO
Dymeng Services Inc.
Business Software Solutions
Go to the top of the page
 
jleach
post Jul 1 2020, 04:56 AM
Post#2


UtterAccess Administrator
Posts: 10,583
Joined: 7-December 09
From: St. Augustine, FL


We're a little late on posting this one, but at least the fix turnaround time was much better than it has been in the past...

--------------------
Jack D. Leach
Founder & CEO
Dymeng Services Inc.
Business Software Solutions
Go to the top of the page
 


Custom Search


RSSSearch   Top   Lo-Fi    11th July 2020 - 11:39 AM