Support – Compile in Hidden Module frmGetRange

Compile Error in Hidden Module frmGetRange

Error in frmGetRange

When using any tool in Quantum XL, SPC XL, or DOE Pro that uses Excel’s refEdit control, the user receives an error starting with “Compile error in hidden module: frmGetRange”

Solution – Disable Safe Mode in ActiveX Settings 

Please consult your IT department before making these changes
  • From Excel select “File” then “Options” (Options is in the lower left corner)

  • Click the “Trust Center Settings” Button

  • Select “ActiveX Settings”

  • Select “Prompt me before enabling Unsafe for Initialization (UFI) controls with additional restrictions for Safe For Initialization (SFI) controls with minimal restrictions” (preferred) OR if that doesn’t work “Prompt me before enabling all controls with minimal restrictions”

  • Uncheck “Safe mode (helps limit the contro’s access to your computer”

ActiveX_PromptBeforUFI
ActiveXSafeMode

Alternative Solution

Quantum XL – Windows Defender ASR Rules

Quantum XL requires read/write access to the Windows Registry and the ability to create child processes (DLLs). For most user’s this is not a problem. However, IT departments who implement the following Attack Surface Reduction (ASR) rules will not be able to run Quantum XL.
  • Rule {D4F940AB-401B-4EFC-AADC-AD5F3C50688A} — “Block all Office applications from creating child processes”
  • Rule {92E97FA1-2EDF-4476-BDD6-9DD0B4DDDC7B} – “Block Win32 API calls from Office macros”
Depending on the configuration of the user’s PC, a variety of errors can occur. Other security applications have similar settings under different titles.

Solution

  • Exclude the installation folder: “%Program Files(x86)%”\SigmaZone\Quantum XL (typically C:\Program Files (x86)\SigmaZone\Quantum XL)
  • Exclude all of the .xlam files in “%Program Files(x86)%”\SigmaZone\Quantum XL