SOLVED

How old is VLOOKUP?

Copper Contributor

To this day, I still get requests for help using VLOOKUP and see new blog posts teaching basic usage. Given the improvement with XLOOKUP, I'm wondering just how long VLOOKUP has been around. Excel 95? Excel 4.0? I just don't know and haven't found function reference lists that old. Would like to use that as a story point for change management.

5 Replies

Ha! Found the answer immediately after posting in @JoeMcDaid's post on Announcing XLOOKUP.

 

According to Joe, "VLOOKUP has been with Excel from the beginning; it was included in Excel 1 for Macintosh released in 1985. For 35 years, VLOOKUP has been the first lookup function learned by Excel users and our 3rd most used function (after SUM and AVERAGE)."

 

35 years for Mac! 33 years for Windows!

best response confirmed by ExcelTL (Copper Contributor)
Solution

@ExcelTL It's actually a little older, that's when it arrived in Excel.

 

I believe VLOOKUP first appeared in Lotus 1-2-3 which predated Excel. According to Wikipedia, Lotus 1-2-3 launched in January 1983, so VLOOKUP appeared sometime around then. VLOOKUP was actually the successor to the original lookup style function, LOOKUP(), which first appeared in VisiCalc in 1979. LOOKUP was created to help with Bob Frankston's tax return. You can read about it here.

 

LOOKUP and VLOOKUP have an amazing history, dating all the way back to the very early days of spreadsheeting. Hats off to the early spreadsheet pioneers. 

@JoeMcDaid 

 

I can testify to personal experience using VLOOKUP with Lotus 1-2-3 in spreadsheets in the time period of 1983-5. I was director of HR for a division of a major (Fortune 50) corp......and one of the first computer geeks to get turned on to how easily one could do all kinds of fancy things for modeling, say, compensation plans. I can recall nesting an HLOOKUP within a VLOOKUP (or maybe it was the other way around), doing some of the things that INDEX and MATCH can do........

 

I can also recall taking the user manuals home on the train, reading about every function, going "Ah ha, that's an easier way to _________" and thinking I can't wait to get back to the office tomorrow to try it out on that big shared-around-the-office PC.

 

How things have changed.

Just thought of a quick PS to my testimonial on VLOOKUP.

 

In 1971 I was working at the IBM Programming Center--where the compilers for Fortran and Cobol were written-- I was in the HR group for the location, but got friendly with some of the programmers. One of them taught me the basics of programming and I started doing my work on a teletype terminal (!!), writing routines that would run on the big system in the basement.

 

I taught myself APL (clever acronym for A Programming Language), a language that was really adept at multi-dimensional arrays. And I started writing routines then that would do some of the analyses that we had to perform....so that pre-dated even VisiCalc, and did involve learning how to address virtual cells in three- and four-dimensional (rarely needed more) arrays. I loved it!

 

VLOOKUP, XLOOKUP, INDEX, MATCH --- they're all child's play.

@ExcelTL 

In this video Excel: Bill Jelen: "From 1979 -- VisiCalc and LOOKUP"! is the demo of how it worked. Interesting. Even if I had some limited experience with VisiCalc, I totally forgot how it was.

1 best response

Accepted Solutions
best response confirmed by ExcelTL (Copper Contributor)
Solution

@ExcelTL It's actually a little older, that's when it arrived in Excel.

 

I believe VLOOKUP first appeared in Lotus 1-2-3 which predated Excel. According to Wikipedia, Lotus 1-2-3 launched in January 1983, so VLOOKUP appeared sometime around then. VLOOKUP was actually the successor to the original lookup style function, LOOKUP(), which first appeared in VisiCalc in 1979. LOOKUP was created to help with Bob Frankston's tax return. You can read about it here.

 

LOOKUP and VLOOKUP have an amazing history, dating all the way back to the very early days of spreadsheeting. Hats off to the early spreadsheet pioneers. 

View solution in original post