Importing data from Excel but not getting results

[UnsolvedCoding]

I have been given the task of debugging a spreadsheet that won't import properly from Excel.

There is only one column that is missing information and even though the table is set to a varchar (10) and only 4 characters are needed. The two missing fields in Excel are numeric only instead of start with a letter like the other fields in the column.

All the fields on the spreadsheet are set to general formatting in Excel and the other columns with alpha-numeric / numeric mixes import correctly.

We have tried a significant number of ideas to get the import to work properly and can't do it.

Does anyone know why only those two cells wouldn't import at all when other cells in different rows import correctly?

 

[SkipVought]

hi,

are numeric only

as compared to all the others that are Alpha Numeric, RIGHT?

CONVERT ALL data in this column to TEXT. FORMAT does NOTHING to the underlying data -- it is merely a DISPLAY FEATURE.

Prepend an APOSTROPHY to all numeric values, like [highlight]'12345[/highlight]!

Skip,
[sub]
Just traded in my old subtlety...
for a NUANCE![/sub]

 

[UnsolvedCoding]

The ' for numerics didn't change anything. I will check if text works.

 

[SkipVought]

what are the values that have a problem?

what are some other values in the column that work ok?

Skip,
[sub]
Just traded in my old subtlety...
for a NUANCE![/sub]

 

[UnsolvedCoding]

The values that are giving problems are straight integers like 811 and 264. All other values including those that start with a letter (like H355) work fine.

 

[SkipVought]

Are you are saying that changing the Excel data from 811 to [highlight]'811[/highlight] and SAVING the workbook, makes no difference.

Are ANY of the NUMERIC values in question in the first 8 rows of data?

Skip,
[sub]
Just traded in my old subtlety...
for a NUANCE![/sub]

 

[UnsolvedCoding]

No other data was in question. The workbook was saved several times and there was no difference.

Since it was only a couple of locations we ended up correcting the problem directly in SQL due to deadlines.

 

[UnsolvedCoding]

Turns out we have a problem with the import wizard.

Thanks anyway Skip.