We have a current Core FOCUS process where people run a fex and save the output into LOTUS format then manually ftp it to their hard drive. They cut and paste the data into a different workbook where one tab performs a VLOOKUP against the tab containing the newly pasted data. If I run this same query in WF in EXL2K format and do the other steps which they perform the vlookup function fails. Both outputs have the data as 'General' format. I'm assuming that even though to the naked eye the LOTUS and EXCEL spreadsheets look the same there is something different that I'm not seeing. If anyone has any insight into using VLOOKUP with EXL2K spreadsheets from WF I'd appreciate any pointers.

WF Reporting Server and Core FOCUS are both on the same HP UX box. WF 7.1.4, Core FOCUS is 6.9

Thanks...

Linus
it depends on the field.
GEneral format doesn't mean much.
If the field (base of vlookup) is numeric,
then compare its value with the VALUE(a1) function, to the field in the lookup table.
If alpha, then compare using a straight compare
=A1=Sheet2!A1, and if you get a FALSE, which i expect you will, you can then investigate why the 2 fields don't match.
Remember, if the field is numeric, excel likes to carry alot of decimal places under the covers, so you need to pay special attn.

As I recall, lotus format is just a comma delimited file, which means the way it's handled in a spreadsheet would be different from an xls format, would by my guess.

Linus,

If you are using Excel templates then I think that your real problem is possibly that your lookup reference is made to a sheet range and not a named range within Excel.

As I have mentioned recently, when WF outputs to an Excel template it actual creates a "new" sheet and therefore the name is different to what you'd expect.

When ever I output to Excel, if I want anything other than what WF can supply easily, I rely upon macros to achieve the required result. So essentially I use WF to supply the data extract into Excel (using push rather than pull as in an Excel query).

You can use WF to name a range (I think?) and you could utilise that facility for your VLOOKUP perhaps?

T

Actually, what's happening is the end user is re-formatting the spreadsheet used for the vlookup every time they paste the data into the spreadsheet. End user behavior is beyond my control.

Easily solved, chop off their fingers or remove their keyboard - the latter option tends to be less messy though

T

Careful Tony, you'll have her thinking about the fingers thing.

You know me too well Pat!

I find carrying a nice pair of secateurs in the back pocket keeps the user base honest The anvil variety tend to give a cleaner cut than the shear type.

T

ROTFLMAO