I'm using a custom scrollbar control, from the Forms 2.0 Object Library.
It is an OLE class, Microsoft Forms 2.0, Forms.ScrollBar.1
It works most places, but one of my computers, trying to set the value .Max crashes with error 483, Object doesn't support his property of method. In a working machine, the class has 70 properties, in the one that crashes, the same class shows only 67 properties. And when I list them, none of them is named Max, in either machine. But the exact same code works on one and crashes on the other. I tried copying the FM20.DLL file, supposedly the source for the control, from the working machine to the crashing one, recompiled the app and no difference. Still crashes and still shows only 67 properties. Not just setting - any reference to the .Max property throws the error. Same with .Min.
It works on my primary dev machine and (so far) on all user's machines, but the one it crashes on is hooked to a live version of the database. I use it to troubleshoot user problems, and sometimes directly do data operations for users, when they want some one-off oddity that I can simply do in a fraction of the time it would take to explain it. It's kind of important that it also work, and since I don't know what's wrong, I'm worried that a user's machine may suddenly also decide to throw a fit.
It is an OLE class, Microsoft Forms 2.0, Forms.ScrollBar.1
It works most places, but one of my computers, trying to set the value .Max crashes with error 483, Object doesn't support his property of method. In a working machine, the class has 70 properties, in the one that crashes, the same class shows only 67 properties. And when I list them, none of them is named Max, in either machine. But the exact same code works on one and crashes on the other. I tried copying the FM20.DLL file, supposedly the source for the control, from the working machine to the crashing one, recompiled the app and no difference. Still crashes and still shows only 67 properties. Not just setting - any reference to the .Max property throws the error. Same with .Min.
It works on my primary dev machine and (so far) on all user's machines, but the one it crashes on is hooked to a live version of the database. I use it to troubleshoot user problems, and sometimes directly do data operations for users, when they want some one-off oddity that I can simply do in a fraction of the time it would take to explain it. It's kind of important that it also work, and since I don't know what's wrong, I'm worried that a user's machine may suddenly also decide to throw a fit.
