At first (and second and third!) reading this sounds like a difference in the way Monarch's Excel interpreter interprets the cell in the worksheet but, out of interest, is that cell in a consistent CHARACTER column or is it a mixed column of Character and Numeric cells? (I assume it is the exact same worsheet you are using in the 2003/2007 comparisons.)
What I'm thinking is that knowing whether, for example, the 2003 interpreter reads a numeric and converts to character whereas the 2007 does not conversion OR the 2007 interpreter, perhaps, reads each cell and ignores the current type, re-inerpreting on the way in.
As Excel can have cell level types but Monarch required a field (column) to be of a single type I would guess that there is some interpretation checking required whichever way things are done.
I would guess that you could do the comparison via a further interpreter field. How complex that might become would depend on whether the Excel column was ALWAYS Numeric or could be a mix on some occasions.
Just 'thinking aloud' at the moment.
I'm inclined to think it is a difference in the Excel interpreter as well.
The column is a consistent character column. Interestingly, even if all of the cells in the column contain all numeric characters, if 1 of them has a leading zero then the column is pulled in as text.
The lookup spreadsheets are created by the first of two projects creating a report. For now I will just plan on exporting the lookup to an Excel 2003 spreadsheet. However, I wish Monarch v10 had the ability to specify the column type when setting up a lookup.
I have some spreadsheet that I need to import that have the same problem. What I hav edone is convert the offending column(s) to text before importing thru Monarch.
Here is a link showing a couple of options.[url=http://www.monarchforums.com/showthread.php?t=284&highlight=excelcolumnstext] Columns to Text /url. Hope these help.