Solution STOCKHISTORY Function is not working compiled with Latest XLS Padlock 2026.1

The thread has a solution
The Excel file is complied with the Latest XLS Padlock 2026.1.
1785479901206.webp
Perform a workbook recalculation at startup is check.
The STOCKHISTORY Function is not working with complied exe file whereas xlsm file its working perfect.
Kindly provide resolution.
 
Solution
STOCKHISTORY is a Microsoft "connected experience": the function does not compute anything locally, it fetches the price history from Microsoft's online service. That is the key to what you are seeing, and it explains why the workbook behaves differently once compiled while the .xlsm works perfectly.

XLS Padlock 2026 can switch Microsoft connected experiences off inside your protected application. When that option is off, the compiled app tells Excel to disable connected experiences that analyse content, and STOCKHISTORY is one of them, so it simply cannot reach the data service any more. Recalculation is not involved, which is why ticking "Perform a workbook recalculation at startup" changed nothing.

So the first thing to check, and...
STOCKHISTORY is a Microsoft "connected experience": the function does not compute anything locally, it fetches the price history from Microsoft's online service. That is the key to what you are seeing, and it explains why the workbook behaves differently once compiled while the .xlsm works perfectly.

XLS Padlock 2026 can switch Microsoft connected experiences off inside your protected application. When that option is off, the compiled app tells Excel to disable connected experiences that analyse content, and STOCKHISTORY is one of them, so it simply cannot reach the data service any more. Recalculation is not involved, which is why ticking "Perform a workbook recalculation at startup" changed nothing.

So the first thing to check, and most likely all you need:

  • Open your project in XLS Padlock and go to the Cloud & AI page.
  • Look for "Allow Microsoft connected experiences".
  • Tick it, rebuild, and test STOCKHISTORY in the new EXE.
Worth knowing before you decide: that option covers the whole family, so enabling it also re-enables Copilot, Python in Excel, Smart Lookup, Translator and Designer inside your application, and cell content may be sent to Microsoft's cloud services. That is inherent to how STOCKHISTORY works, since the data has to come from Microsoft, but it is a deliberate trade-off rather than something to switch on without thinking, especially if your workbook holds sensitive data.

Please tell us which case you are in, because it decides what comes next:

  • If the option was off and ticking it fixes STOCKHISTORY, you are done.
  • If the option was already on and STOCKHISTORY still fails, tell us, because then it is something else and we want to look at it properly rather than guess. In that case it would help to know whether the cells show an error value, stale data, or nothing at all.
 
Solution
Back
Top