|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
linked server to Excel
We've created a linked server to access an Excel spreadsheet that resides on
the same server as SQL Server 2000. If we log on to the database server (Windows 2000), then launch Enterprise Manager, the linked server works perfectly. But, if we launch Enterprise Manager from a desktop machine (Windows 2000) and attempt to use the linked server we get: "Error 7399 : OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error." Any ideas? SELECT *
FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0', 'Data Source="c:\test.xls";User ID=;Password=;Extended properties=Excel 5.0')...[test1$] And the 'test1' is the name of work sheet. Show quoteHide quote "Vince" wrote: > We've created a linked server to access an Excel spreadsheet that resides on > the same server as SQL Server 2000. If we log on to the database server > (Windows 2000), then launch Enterprise Manager, the linked server works > perfectly. > > But, if we launch Enterprise Manager from a desktop machine (Windows 2000) > and attempt to use the linked server we get: "Error 7399 : OLE DB provider > 'Microsoft.Jet.OLEDB.4.0' reported an error." > > Any ideas? > > > Thanx for the response.
However, I get the same result. Show quoteHide quote "luyan" <lu***@discussions.microsoft.com> wrote in message news:FFE5CD8B-ED99-4568-8B55-21AB6A73242C@microsoft.com... > SELECT * > FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0', > 'Data Source="c:\test.xls";User ID=;Password=;Extended properties=Excel > 5.0')...[test1$] > > And the 'test1' is the name of work sheet. > > "Vince" wrote: > > > We've created a linked server to access an Excel spreadsheet that resides on > > the same server as SQL Server 2000. If we log on to the database server > > (Windows 2000), then launch Enterprise Manager, the linked server works > > perfectly. > > > > But, if we launch Enterprise Manager from a desktop machine (Windows 2000) > > and attempt to use the linked server we get: "Error 7399 : OLE DB provider > > 'Microsoft.Jet.OLEDB.4.0' reported an error." > > > > Any ideas? > > > > > >
Other interesting topics
Sql Server 2005 - SMS "Modify Table option" times out when trying to 'alter' very large table
SQLExpress Rename Cluster Instance - New Hardware - Keep Name Moving the SQL 2005 System Tables Microsoft doesnt really support anything over 32 Databases(??) Slow performance Can I use SQL Express database inside full blown SQL 2005? SQL Server CPU Spikes Object search query??? Database refresh |
|||||||||||||||||||||||