Greg Truby
MrExcel MVP
- Joined
- Jun 19, 2002
- Messages
- 10,030
OK - since ain't nobody up an' said it, I will. Like Richard I'll use VLookup() when fetching ta the right and Index(Match()) when fetchin' left. What I won't do, is to pop in a UDF - in spite of the ease of writing one. Mainly because of the VBA security crapola. Yes, I could digitally sign the workbook. Yes, I could have the user install my digi-sig if he ain't got it (assuming, of course, that his security is set to medium and not high or VH). Or, I could put the code in a custom add-in, that would at least make it more "accessible" to the workbook. But then I'd have to distribute the add-in. And all of this to avoid using Index(Match())? Blech!
Now I'll get off'n the soapbox and just nod my head in that yes, I too cannot figure out why the fellers that wrote it didn't let 'er look ta the right 'n' fetch from the left too.
The other burr under my saddle is having ta specify the entire range yer lookin' into. More'n once I've gotten a blasted #REF! error 'cause I want a column that's off the right end of my "table_array" and I gotta go back and widen 'er up a bit. A while back I figured out that this "pass in the whole table" bit would be necessary for the function to process "hard-coded" arrays, in addition to ranges. But I woulda hoped the fellers that wrote the function coulda made 'er smart enough to have it behave differently based on the type of input received. ['course considerin' the thing don't even "fetch left", I reckon I ought not to be surprised. ]
Now I'll get off'n the soapbox and just nod my head in that yes, I too cannot figure out why the fellers that wrote it didn't let 'er look ta the right 'n' fetch from the left too.
The other burr under my saddle is having ta specify the entire range yer lookin' into. More'n once I've gotten a blasted #REF! error 'cause I want a column that's off the right end of my "table_array" and I gotta go back and widen 'er up a bit. A while back I figured out that this "pass in the whole table" bit would be necessary for the function to process "hard-coded" arrays, in addition to ranges. But I woulda hoped the fellers that wrote the function coulda made 'er smart enough to have it behave differently based on the type of input received. ['course considerin' the thing don't even "fetch left", I reckon I ought not to be surprised. ]