Re: <VB 2008> Use ADO.net 3.5 to connect with Excel 2003
- From: "Gregory A. Beamer" <NoSpamMgbworld@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Aug 2009 09:24:38 -0700
sam <sam@xxxxxxxxx> wrote in news:eeL6FI1HKHA.3928@xxxxxxxxxxxxxxxxxxxx:
Hi,__b77a5c56
I try to connect to Excel 2003 xls using OLDBConnection object. And
I
use this connection String:
Dim str As String
str = "OLEDB;Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\Data1.xls;Extended Properties=""Excel 8.0;HDR=Yes;"""
cnn = New OleDbConnection(str)
cnn.Open()
da = New OleDbDataAdapter("Select * From Employee", cnn)
da.Fill(ds)
DataGridView1.DataSource = ds.Tables(0)
It give me no exception but my DataGridView is empty.
And after I stop debug, it give me this in output windows
The thread 0x1798 has exited with code 0 (0x0).
The thread 0x1610 has exited with code 0 (0x0).
'ExcelDB.vshost.exe' (Managed): Loaded 'C:\Users\Thit\Documents\Visual
Studio 2008\Projects\ExcelDB\ExcelDB\bin\Debug\ExcelDB.exe', Symbols
loaded. 'ExcelDB.vshost.exe' (Managed): Loaded
'C:\Windows\assembly\GAC_MSIL\System.Runtime.Remoting\2.0.0.0
1934e089\System.Runtime.Remoting.dll', Skipped loading symbols. Module
is optimized and the debugger option 'Just My Code' is enabled.
A first chance exception of type 'System.ArgumentException' occurred
in System.Data.dll
The thread 0x13ac has exited with code 0 (0x0).
The thread 0x171c has exited with code 0 (0x0).
The program '[5520] ExcelDB.vshost.exe: Managed' has exited with code
0 (0x0).
I try to google and everywhere give me the same connection string.
Even I take out all statements after cnn.open()
I still get the sam message in my output window.
What
OS?
Version of .NET?
These could be important to the answer. Regardless, try the rest of the
post and see if it helps.
The OLEDB providers for JET shipped separately from the standard MDAC.
In some versions of .NET, if not all, you have to install JET
separately. I cannot find the download page, but there is a download
page for the JET providers somewhere. This KB
(http://support.microsoft.com/default.aspx/kb/239114) has a download,
but it is not all OSes.
The JET providers are supposed to be pushed out through windows update
now, so check if you have ignored that download and install (may be in
non-mandatory, so custom install may be needed).
Note that the Office 2007 driver is different:
http://snurl.com/qdtbx
NOTE that there was no 64 bit driver for JET for some time. If you ran
on a 64-bit machine, you ended up having to downgrade to 32-bit for your
web apps to have things running. I would assume this is updated by now,
but I don't run Access on my websites.
Peace and Grace,
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com
*******************************************
| Think outside the box! |
*******************************************
.
- Follow-Ups:
- Re: <VB 2008> Use ADO.net 3.5 to connect with Excel 2003
- From: Mark Rae [MVP]
- Re: <VB 2008> Use ADO.net 3.5 to connect with Excel 2003
- From: sam
- Re: <VB 2008> Use ADO.net 3.5 to connect with Excel 2003
- References:
- Prev by Date: <VB 2008> Use ADO.net 3.5 to connect with Excel 2003
- Next by Date: Entity Framework, Inheritance and Deleting
- Previous by thread: <VB 2008> Use ADO.net 3.5 to connect with Excel 2003
- Next by thread: Re: <VB 2008> Use ADO.net 3.5 to connect with Excel 2003
- Index(es):
Relevant Pages
|
