RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2024-08-21T13:53:55Z
I am migrating a 32-bit Access project to 64-bit Access. I am replacing all the older 32-bit iGrid 6.5 objects with the new 64-bit iGrid 7.5.

I am getting an "application-defined or object-defined error" error that I tracked down to the BackColor property.

error.png

Click to View Image6 View(s)


error02.png

Click to View Image8 View(s)

RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2024-08-21T15:21:49Z
I was getting this error all morning and now the error is gone. I have no idea what changed but it is working now.
Igor/10Tec
2024-08-21T15:30:20Z
If you can ever reproduce this problem in a new database, send it to us for the further consideration.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2024-08-22T14:21:12Z
It is happening again.
  Testing.zip (23kb) downloaded 3 time(s).
Igor/10Tec
2024-08-23T14:56:52Z
It works ok on my pc.

Can you try to reproduce the problem on other computers and if possible, in different versions of Microsoft Office?
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2024-08-23T15:03:25Z
Yes, I can find another computer to test on. But all our computers use the same (latest) version of M365. Would you be interested in a remote session to see the problem?
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2024-08-23T15:25:21Z
The error number is not always the same. Despite the error, it does set the BackColor to the light blue.

I assume you saw the single line of code in the form's Load event. If I comment out that line, the error goes away.

64_error_02.png

Click to View Image6 View(s)


64_error_03.png

Click to View Image5 View(s)


64_error_01.png

Click to View Image5 View(s)

Igor/10Tec
2024-08-26T10:27:37Z
Do we need to run the form many times until the error appears?
Igor/10Tec
2024-08-26T15:37:00Z
Strange. Today it happened 2 times right after opening the database. Just 2 first times, and then no problems. Note that I closed/re-opened Microsoft Access every time.

A very strange issue. To report this problem to Wayne Phillips, the developer of twinBASIC (the tool we used to compile the modern edition of iGrid OCX), we need a sample that allows us to reproduce the issue in a stable manner.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2024-08-26T22:11:37Z
I tested on several computers today and they are all getting the error.

I have no idea why it works sometimes and not other times and so I cannot think of how to create a sample where it always errors.
Igor/10Tec
2024-08-27T14:40:35Z
Well, I will pass this bug report to Wayne. Perhaps, he will eventually find the root of this problem and fix it. Иut no one can give you a more or less precise time when it will happen.

Have you ever experienced the same problem with another property of iGrid? I tried to replicate it with ForeColor but couldn't.

And what is also strange, the iGrid.BackColor property works fine in VBA UserForms. Most likely, it is a specific issue that occurs only in Access.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2024-08-27T16:20:32Z
BackColor is the only property that has given me an error.

I don't know what you mean when you say it works in VBA UserForms but not in Access forms. Those two things are the same in my mind. Did you mean VB user forms?

I realize you have no control over how quickly this gets resolved. I appreciate whatever you can do.

Thank you, Igor.
Igor/10Tec
2024-08-28T06:50:21Z
VBA UserForms is what you can use in Word/Excel VBA to create dialogs for the user. This form package is completely different from MS Access forms.
Igor/10Tec
2024-10-10T09:51:06Z
Have just sent you an email with the link to the latest interim build of iGrid to try.
RaymondC
  • RaymondC
  • Advanced Member Topic Starter
2024-10-22T14:29:05Z
The new build has solved the problem. Thank you.