Re: Fields with mixed string/number data
- From: Peter A <paitken@xxxxxxxxxxxxxx>
- Date: Thu, 25 Jan 2007 09:34:36 -0500
In article <OqLzShIQHHA.4156@xxxxxxxxxxxxxxxxxxxx>, reb01501
@NOyahoo.SPAMcom says...
There was no way for you to know it (except maybe by browsing through
some of the previous questions in this newsgroup before posting yours -
always a recommended practice) , but this is a classic ADO newsgroup.
ADO.Net bears very little resemblance to classic ADO so, while you may
be lucky enough to find a dotnet-knowledgeable person here who can
answer your question, you can eliminate the luck factor by posting your
question to a group where those dotnet-knowledgeable people hang out. I
suggest microsoft.public.dotnet.framework.adonet.
Unfortunately, I've never used ADO or ADO.Net to retrieve spread***
data, so I cannot answer your question.
Thanks, I will look for an ADO.Net newsgroup. In the interim I found the
solution, to include IMEX=1 in the Extended Properties part of the
connection string. This tells the Jet engine to read all data as
strings.
--
Peter Aitken
.
- Follow-Ups:
- Re: Fields with mixed string/number data
- From: Bob Barrows [MVP]
- Re: Fields with mixed string/number data
- References:
- Fields with mixed string/number data
- From: Peter A
- Re: Fields with mixed string/number data
- From: Bob Barrows [MVP]
- Fields with mixed string/number data
- Prev by Date: Re: Fields with mixed string/number data
- Next by Date: Re: Fields with mixed string/number data
- Previous by thread: Re: Fields with mixed string/number data
- Next by thread: Re: Fields with mixed string/number data
- Index(es):