RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2020-06-07T17:52:25Z
It seems that a recent Windows 10 update has broken iGrid (v6.5.84).

I am getting automation error on all PCs:
error1.jpg

Edit: More info:
I upgraded all our Windows 10 PCs this weekend to version 1909 and that broke iGrid. I have one PC that is still on version 1903 and it works correctly.
Igor/10Tec
2020-06-08T06:44:41Z
Windows 10 v1909 is not the latest update now, now it's v2004.

v1909 was released in autumn and it is being used by many customers together with iGrid without any problems. You are the first who reported this issue.

Have you tried re-register iGrid in the Windows registry? Perhaps, the ActiveX registration records were cleared after the upgrade, and you just need to re-create them.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2020-06-08T13:32:47Z
Hi,

v2004 is not widely available. Only a few of our PCs have the option to install v2004.

Yes, I did try re-registering iGrid but it did not work.

It is very strange that this is only happening to me. I have three different Access applications that all use iGrid. The only thing I did was install the 1909 patch and it broke all three apps on all 26 PCs. This is not a problem with just one app or just one PC. I tested the other code in Access and the error only happens when I call iGrid functions. I will do some more testing.

Ray

Edit: I have concluded that this error is NOT related to the 1909 Windows update. I found one PC that was still on v1903 and it also has the same error. I will keep investigating.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2020-06-08T15:20:24Z
Update:

I have discovered that the error only happens when I try to populate an iGrid column with data of type DECIMAL.
Igor/10Tec
2020-06-08T15:33:41Z
I do not exclude that this can be a problem inside iGrid. But if you know your apps worked with iGrid without any problems for years before an update, then yes, most likely the problem is outside of iGrid. Nothing related to data population has changed in it during last few years.

Try to localize the problem and find the culprit. Even if the problem is outside of iGrid, tell us and other developers here what we should not do because there is an issue in the Microsoft data access stack.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2020-06-08T15:53:42Z
The apps have indeed worked for years without any problems. Perhaps Microsoft updated Access such that it no longer works correctly with the DECIMAL data type.

The attached database can be used for testing. The button "add double data" works but the button "add decimal data" does not.

  decimalproblem.zip (30kb) downloaded 1 time(s).
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2020-06-08T16:24:13Z
More info: All of my Access tables are actually linked SQL Server tables. SQL Server does not have the double data type so I am stuck with the decimal data type.

I tested that if I modify my SQL statement to convert the data before populating it into iGrid, then it works. For example, "SELECT CDbl(DecimalData) AS ConvertedData FROM Table1."

I have hundreds of SQL statements in my apps so this would be a tedious solution. It would be awesome if there was something inside of iGrid that could solve this, but I realize that this may be an Access problem and there is nothing you can do.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2020-06-08T19:14:43Z
It looks like this problem is not just with iGrid.

A simple record update in VBA that has worked for years, no longer works.

R.AddNew
R![MyDecimalData] = 12.5
R.Update

Also, converting to decimal does not work:

R.AddNew
R![MyDecimalData] = CDec(12.5)
R.Update

I am going to try upgrading my SQL Server Express 2014 to the newest version.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2020-06-09T02:01:07Z
There seem to be a number of posts related to:

Access Update 2005 12827.20268 (released June 2, 2020)

This update is only 6 days old so I bet Microsoft fixes it soon. I’m so glad to see that I am not going crazy!

https://www.devhut.net/2...-20268-causing-problems/ 
Igor/10Tec
2020-06-09T15:21:34Z
I downloaded your Access database and tried to reproduce the problem in VB6 IDE under the debugger. I tried to connect to your database using the Microsoft ActiveX Data Objects 6.1 library. I create an ADODB.Connection to your accdb and then try to show the records with a simple code like this:

Dim R As Recordset
Set R = cn.Execute("SELECT TestID, DecimalData FROM Table1")

If R.RecordCount <> 0 Then
    iGrid1.FillFromRS R
End If


And know what? The whole VB IDE closes randomly after executing this code. However, sometimes I have 2-3 seconds to see the recordset in iGrid before the VB IDE closes. That means the FillFromRS method works, but the automation error occurs outside of the VB6 IDE thread with iGrid.

Even if I remove that If statement with FillFromRS inside, the result is the same - random crashes of the VB IDE.

It's evident that the problem is outside of iGrid and VB6 IDE.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2020-06-09T16:47:05Z
Yes, Microsoft made an official post acknowledging the problem. They suggest rolling back to a previous build of Access (from v2005 to v2004) . I did that this morning and it all works correctly again. Crazy!