Re: ISAM error related to Excel 2003 Jet Engine on Server 2003 SP2

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Apr 20, 10:56 am, "Cor Ligthert[MVP]" <Notmyfirstn...@xxxxxxxxx>
wrote:
Jim,

You have checked out all this?

http://www.connectionstrings.com/excel

Cor

"JimLad" <jamesdbi...@xxxxxxxxxxx> wrote in message

news:7ca8a3dc-2357-4a73-906b-a4e1396d6b49@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Apr 17, 2:51 pm, "sloan" <sl...@xxxxxxxxx> wrote:





3 quotes now come to mind:

/*> sorry for my previous post i found that there was an error in the
connection string ie excel8.0 instead of excel 8.0

*/

//Quote
A space in the filename, a missing single quote...any of them can kill
you.
You have to SUPER ANALLY examine your connection string.
//End Quote

//
Definitely not the connection string.//

That's why I asked for you to post the actual connection string(s).
If you're seeking help, then that would have been a simple thing to do.

Good luck dude.

"Cor Ligthert[MVP]" <Notmyfirstn...@xxxxxxxxx> wrote in message

news:%23wZgibyvJHA.3504@xxxxxxxxxxxxxxxxxxxxxxx

Jim,

In this long forum discussion about this, there is called a solution, it
is like this.
\\\
hello friends,

sorry for my previous post i found that there was an error in the
connection string ie excel8.0 instead of excel 8.0

that make the problem.

Regards

Prathap

///

Cor- Hide quoted text -

- Show quoted text -

Hi,

We have tried several connection strings - all work on our dev
machine, but not on live:

_connectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=TestData1.xls;Extended Properties=""Excel 8.0;IMEX=1"";"

      <add name="ExcelConnectionString"
connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=FILE_PATH;Extended Properties='Excel 8.0;IMEX=1'"
providerName="System.Data.OleDb" />

We have tried single quotes and doubles quotes on the extended
properties. We have also proved that reverting the registry key fixes
the problem.

Another point to note is that we don't have the win32old registry key
on the live server.

Any help would be great. I still don't think it's the
connnectionstring that's the problem, but I will try anything that
people mention...

James- Hide quoted text -

- Show quoted text -

Sticking OLEDB; on the front didn't work anywhere.

Sticking in HDR=Yes; as opposed to just letting it default, did not
made a difference.

Any other ideas?

James
.

Relevant Pages

  • Re: ISAM error related to Excel 2003 Jet Engine on Server 2003 SP2
    ... a missing single quote...any of them can kill you. ... You have to SUPER ANALLY examine your connection string. ... We have tried single quotes and doubles quotes on the extended ... Another point to note is that we don't have the win32old registry key ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: ISAM error related to Excel 2003 Jet Engine on Server 2003 SP2
    ... quotes now come to mind: ... connection string ie excel8.0 instead of excel 8.0 ... a missing single quote...any of them can kill you. ... You have to SUPER ANALLY examine your connection string. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Hide a cell so that users cant see the contents
    ... thank you Paul for the inspiration. ... a cell equal to the name and that dropped the quotes. ... to use it to build your connection string. ...
    (microsoft.public.excel.programming)
  • Re: Thanks, but it doesnt work with .Net
    ... Here is my original connection string in my app.config file. ... when I realized I'd left out the double quotes in Paul's ... > Hi Geoff, ... > you post your connection string with IMEX here? ...
    (microsoft.public.vb.database.ado)
  • Help with String.Format
    ... require quotes around the values within the connection string. ... Note the quotes around the Extended Properties values. ... Where Provider, FilePath, ExtendedProperties, SheetHeader are all vars ...
    (microsoft.public.dotnet.languages.csharp)