Leaderboard

@Drew_Brosenhaus, see here: https://ibkr.info/node/2155 Probably your Excel and TWS architecture does not match. For example, this can be if you are using 64-bit TWS and 32-bit Excel or vice versa.

@Drew_Brosenhaus My experience is the same as @Stanislav's. You can compare the time needed for IB API to return historical data to the time it takes when you request a intra-day chart for an options combo in TWS. That can well take even 5 min until the chart is filled. Looks like API connections and charts get their data via the same mechanics under the hood. Yesterday's RV data directly comes from my server and should be returned very fast. It additionally gets cached in the tool.

@Drew_Brosenhaus, on overall, IB TWS is very slow to return historical data. Looks like their architecture had been designed in 1980 and did not change since that time. So when generating Straddle/Calendar RV charts it is ok to wait a minute or sometimes even more while TWS returns all required data. As for Watchlist, I've just checked - works pretty fast. When I type a new ticker into Symbol column, the tool automatically updates expiry, RV and other info in the watchlist. Probably you tried to test this on weekends, and IB does some server maintenance on Saturdays, so TWS does not work correctly till Monday. Try again in trading hours. Also try to type a different ticker into Symbol column.

Are you still observing an error "The ddedll.dll file required for Excel integration is either missing or out of date"? I think your chances of receiving a meaningful answers are better if you prove slightly more info on what is going on on your system. Here are some general suggestions: - Does you TWS arch matches Excel architecture? I.e. TWS 32-bit and Excel is 32-bit. Check in Task Manager that excel.exe and javaw.exe for TWS are both 32-bit processes (or both 64-bit processes); - Did you install latest version of TWS API? Available here: https://interactivebrokers.github.io/# - Ensure that you enabled "Enable Active X and Socket Clients" in Global Configuration/API/Settings; - Check that "Socket port" in TWS settings matches port specified in Excel RV Tool; - Enter Host: 127.0.0.1 in Excel RV Tool (with this field empty the tool did not work on my machine); - Check that C:\Windows\ddedll.dl file exists (you can post here this file, so we can check what architecture this file is for); Finally, if nothing helps, look at "ActiveX Sample Spreadsheet" that comes with TWS API. Usually located here: C:\TWS API\samples\Excel\TwsActiveX.xls. Ensure it works ok. It may also worth to take a look at TwsDde.xls and/or TwsRtdServer.xls samples. Probably there are some issues on 64-bit Windows with 32-bit TWS/32-bit Excel & ddedll.dll. On my system both Excel and TWS are 64-bit applications. Everything works fine, despite the fact that C:\Windows\ddedll.dll file is for 32-bit architecture - most likely this file is not used at all when TWS/Excel are 64-bit. That is proved by the following remark from IBKR article I quoted above: So, your best bet is to switch to 64-bit Excel and 64-bit TWS. This configuration is proven to work. You can also try to close all other applications such as Chrome, VLC Player, Adobe Creative Cloud or Microsoft One Drive, as suggested in the quote above.

Thank you @Stanislav added this version to the download page

I found some time to merge my fixes into Excel 2019 x64 compatible version of the spreadsheet that I released in the post above. Here is the fixed version with "most recent data on RV chart fix" included. Chartaffair Real-Time RV Tool.xlsm