ScrollBar control crashing (2 Viewers)

[pdanes]

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.

 

[CJ_London]

are both machines using the same version and bitness of access and what are they?

 

[tvanstiphout]

ActiveX DLLs like fm20.dll cannot just be copied; they need to be registered.
Open a Command Prompt using Run as Administrator.
On my machine with 32-bit Office:
c:\windows\syswow64\regsvr32.exe C:\Program Files (x86)\Microsoft Office\Root\VFS\SystemX86\FM20.DLL

My version of fm20.dll is only 10 days old and the version is 16.0.19725.20058
Access is on version 2602 MEC.

There is also a chance this file has dependencies that also need to be installed. It gets complicated from there. The best way to install would be to run a setup program, such as Office Repair from Control Panel.

BTW, I do not get the crash. I guess is you have a mismatch of Office components and Office Repair is the next logical step.

 

[arnelgp]

in my case, I set it's Max (or Min) by:

Me.ScrollBarName.Object.Max = somevalue

 

[pdanes]

are both machines using the same version and bitness of access and what are they?

Both are running 64-bit Office 365.

 

[pdanes]

Got it - thank you all. I had 'Disable all controls without notification' set on the ActiveX page in the Trust Center. SMH...

 

[pdanes]

in my case, I set it's Max (or Min) by:

Me.ScrollBarName.Object.Max = somevalue

I tried that, and got a different error: 2929 'Because of your security settings and current security policy, this control is disabled.' But that set me on the track to find the actual error. Thanks for the tip.

 

[isladogs]

Ah yes, you would get error 438 if ActiveX controls are disabled in Access Options. Its one reason why I avoid ActiveX controls as far as possible

Having said that, I do use the MS Forms ActiveX scrollbar in a couple of apps and without needing the MS Forms reference. For example;

Its useful as it can be programmed (unlike the standard scrollbars

I also don't see Min / Max in the list of intellisense properties but it works for me using Me.ScrollbarName.Min = somevalue
If interested, see the example app at:

Freeze Columns in Continuous Forms

This is the third part of a 3-part article which discusses the freeze fields feature in datasheet forms and demonstrates how similar functionality can be added to continuous forms. In this article, I show how the form can also be navigated using tab / shift + tab keys

www.isladogs.co.uk

Its a common issue that ActiveX controls have missing properties in intellisense and even have unlisted event procedures
For example the Slider control doesn't list the undocumented OnScroll event but its necessary to use that control.