Vlookup stopped working

%3CLINGO-SUB%20id%3D%22lingo-sub-1595717%22%20slang%3D%22en-US%22%3EVlookup%20stopped%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1595717%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20written%20a%20c%23%20program%20to%20generate%20an%20excel%20report%20for%20the%20last%208%20years%2C%20but%20suddenly%20and%20without%20explanation%20in%20the%20last%20week%2C%20those%20files%20cannot%20open%20without%20the%20repair%20dialog%20loading%20first.%20I%20believe%20something%20within%20the%208.11.20%20security%20patches%20have%20affected%20the%20vlookup%20functionality%2C%20but%20I%20can't%20find%20any%20updated%20documentation%20that%20explains%20what%20to%20do%20differently.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20vlookup%20refers%20to%20a%20separate%20file%20for%20it's%20source%2C%20so%20I'm%20not%20sure%20if%20that's%20the%20cause%20or%20if%20there's%20another%20issue%20going%20on%3F%26nbsp%3B%20Here's%20what%20the%20vlookup%20looks%20like.%20The%20VLOOKUP%20references%20a%20pricelist%20excel%20file%20for%20it's%20source%20data.%20The%20report%20then%20takes%20the%20price%20and%20multiplies%20by%20quantities%20based%20on%20budgeting%20data%20that%20we%20pull%20from%20a%20database%3A%26nbsp%3B%3C%2FP%3E%3CP%3EVLOOKUP(RC1%2C%5BPriceList.xlsx%5DPrices!%24A%3A%24H%2C6%2CFALSE)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20also%20attached%20what%20it%20looks%20like%20when%20I%20open%20the%20affected%20files.%20I%20just%20can't%20believe%20Excel%20would%20intentionally%20reference%20these%20files%20as%20'corrupt'%20when%20they've%20been%20working%20for%20years.%20Any%20thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1595717%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExcel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFormulas%20and%20Functions%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Regular Visitor

Hi all, 

 

I've written a c# program to generate an excel report for the last 8 years, but suddenly and without explanation in the last week, those files cannot open without the repair dialog loading first. I believe something within the 8.11.20 security patches have affected the vlookup functionality, but I can't find any updated documentation that explains what to do differently.  

 

My vlookup refers to a separate file for it's source, so I'm not sure if that's the cause or if there's another issue going on?  Here's what the vlookup looks like. The VLOOKUP references a pricelist excel file for it's source data. The report then takes the price and multiplies by quantities based on budgeting data that we pull from a database: 

VLOOKUP(RC1,[PriceList.xlsx]Prices!$A:$H,6,FALSE)

 

I've also attached what it looks like when I open the affected files. I just can't believe Excel would intentionally reference these files as 'corrupt' when they've been working for years. Any thoughts?

0 Replies