Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: stcheng@xxxxxxxxxxxxxxxxxxxx ("Steven Cheng")
- Date: Wed, 13 May 2009 02:39:24 GMT
{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Tomplfe,
\par
\par Also, you can try temporarily switch the ASP.NET web app to 32 bit mode(in IIS) so verify whether it is the 64-bit problem.
\par
\par #Configuring IIS to Run 32-bit ASP.NET Applications on 64-bit Windows
\par http://technet.microsoft.com/en-us/library/cc737351(WS.10).aspx
\par
\par http://support.microsoft.com/kb/894435
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
\par
\par \pard\li720 --------------------
\par From: "TompIfe" <tpskonto@xxxxxxxxxxxxxxxx>
\par References: <OO5zPwnyJHA.3968@xxxxxxxxxxxxxxxxxxxx> <wTOWCWGzJHA.4632@xxxxxxxxxxxxxxxxxxxxxx> <eMJXDAkzJHA.1492@xxxxxxxxxxxxxxxxxxxx> <6gwWBcvzJHA.4632@xxxxxxxxxxxxxxxxxxxxxx> <OiG6bR8zJHA.1416@xxxxxxxxxxxxxxxxxxxx> <Ou#1L6O0JHA.5036@xxxxxxxxxxxxxxxxxxxx> <u7TFaRi0JHA.2584@xxxxxxxxxxxxxxxxxxxx>
\par Subject: Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
\par Date: Mon, 11 May 2009 16:28:55 +0200
\par
\par
\par Hi again,
\par
\par I believed that a winform application on the 64 bit machine worked fine
\par because when I added the Access data base to it,
\par a klicked on "test connection" it said OK, and when I pressed 'preview' on a
\par DataGridView of a table in the data base, it was filled with data. However,
\par when I run the winform application, the DataGridView is empty. So the "test
\par connection" and "preview" works despite there is no Jet provider. This seems
\par a bit odd, do not you think? Which mechanisms are used for "test connection"
\par and "preview", and should not an error message been given since the Jet
\par provider is defined in the connection string on the 64 bit machine?:
\par connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data
\par Source=|DataDirectory|\\Test.mdb"
\par
\par Kind regards,
\par TomIfe
\par
\par
\par }
- Follow-Ups:
- References:
- 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- RE: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: "Steven Cheng"
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: "Steven Cheng"
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: Joel Lucsy
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- From: TompIfe
- 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- Prev by Date: Re: I am at a lost.... WCF
- Next by Date: Re: Exception as XML
- Previous by thread: Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- Next by thread: Re: 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
- Index(es):
Relevant Pages
|