Hi KL,

Just like the world is not ...

the problem behind is that too many people are importing/exporting and
transferring data nowadays because it is so "easy" with office
applications. They do not care about anything (you know, the boring
stuff like datatypes and field descriptions) but this is neccessary to
avoid errors - and these errors start eg. in excel when the vlookup
does not work, then complicated formulas are used to fix the problem -
problems that would never come up if you deal with the boring stuff
first.

Your solution is working, for you. Do you think someone who cannot deal
with the boring stuff eg. will be able to find lost brackets {} of your
matrix formula (when you edit the formula an leave it without
ctrl+shift+enter)? Do you think someone else has a chance to really
understand what you did - why did you use ""& in the first part of the
formula, why text() in the second part?

ok, it's working, but it is complicated, hard to understand, not very
common and therefore a good base for any kind of errors. My message is
to solve the problem where it starts.

use with sql statement?
I meant the datatable that is used for the vlookup may be created with
some sql-query.

arno