Issue 80 in linqtoexcel: Column data types

[linqt...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 80 by CliffKGi...@gmail.com: Column data types
http://code.google.com/p/linqtoexcel/issues/detail?id=80

What steps will reproduce the problem?
When reading a column where the first data row is numeric and following
rows are text fields the text fields are ignored


What is the expected output? What do you see instead?
Would like to see all rows read regardless of datatypes. In our case above
the column contains lot numbers, which are sometimes numeric and sometimes
alpha numeric. To get around this issue we either have to mark the column
as text in excel or put a dummy row in fist with a text value.


What version of the product are you using? On what operating system?
1.6.2 on Windows Server 2008r2

Is there a way to set the field datatype as users are not great at
formatting spreadsheets correctly!???

Cheers
Cliff

[linqt...@googlecode.com]

Comment #1 on issue 80 by paulyo...@gmail.com: Column data types
http://code.google.com/p/linqtoexcel/issues/detail?id=80

Cliff,

Can you attach the spreadsheet your're using and also show me the code
you're using to query the spreadsheet.

Thanks,
Paul

[linqt...@googlecode.com]

Comment #2 on issue 80 by crvazq...@gmail.com: Column data types
http://code.google.com/p/linqtoexcel/issues/detail?id=80

Hi all, I am having an issue that I need help with. I am importing a CSV
file with a text column that is supposed to have only numbers, but they can
have leading zeros. After the data is imported, all the leading zeros are
lost. Is there any way to specify column formats or a workaround this
issue? I really appreciate your assistance with this matter.

[linqt...@googlecode.com]

Comment #3 on issue 80 by slawomir...@gmail.com: Column data types
http://code.google.com/p/linqtoexcel/issues/detail?id=80

Hi,
I have simmilar problem. I have an excel column which has fields with
numeric and alphanumeric data. I try to map this column to .net string
type. Only alphanumeric types are retrieved. Numeric data result in null
string. One workaround is to force excel formating to text on that column.
Tested on 1.6.6

best regards
Sławomir

[linqt...@googlecode.com]

Updates:
Status: Fixed

Comment #4 on issue 80 by paulyo...@gmail.com: Column data types
http://code.google.com/p/linqtoexcel/issues/detail?id=80

I believe Slawomir has the best workaround for this issue: force excel
formatting to text on that column

[linqt...@googlecode.com]

Comment #5 on issue 80 by pstem...@gmail.com: Column data types
http://code.google.com/p/linqtoexcel/issues/detail?id=80

So, is there no real "fix" for this? I can't always guarantee the user
will format a column to be text. (I have the same scenario where a column
is usually numbers, but COULD be text. I have my object defined as a
string, but linqtoexcel will ignore the non-numeric values if numeric value
rows come first.)

Thanks

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[linqt...@googlecode.com]

Comment #6 on issue 80 by paulyo...@gmail.com: Column data types
http://code.google.com/p/linqtoexcel/issues/detail?id=80

Sorry, but there is no real "fix" for it. You will have to talk to
Microsoft to update their Jet and Ace database engines to fix it.

[pste...@gmail.com]

Understood.  Would it help if we could override the Extended Properties on the connection string?  I know that JET ignores the MaxScanRows value when passed in the connection string, but I heard ACE does support it.  To use it though, we would need to be be able to pass over customized/modified Extended Properties.

Paul

[linqt...@googlecode.com]

Comment #7 on issue 80 by pzthe...@gmail.com: Column data types
http://code.google.com/p/linqtoexcel/issues/detail?id=80

I'm having something similar where most of my values in the column are
numeric ...but 50 rows down, there is a alpha value. The object thinks
it's a null value. It's a computed value.

Any hints ?

[Florin Adrian Gerlan]

Microsoft says it can solve the problem by putting "IMEX = 1" in "Extended Properties" of connection to excel file.