Who works with Windows Vista 64-bit and the famous OLEDB.4.0 provider for database communication, is
with the error message "The, Microsoft.Jet.OLEDB.4.0' provider
is not registered on the local computer" first make big eyes.
with the error message "The, Microsoft.Jet.OLEDB.4.0' provider
is not registered on the local computer" first make big eyes.
When I was running on a 64-bit system my application for the first time, made me this message for great astonishment.
After I had the mistake pinpointed and fixed (if one in this case, so to speak), were my eyes but even greater.
The beloved, Microsoft.Jet.OLEDB.4.0' provider supports namely no 64-bit. And this is not planned in the future to change!
So what can you do?
It's simple:. Applications that use this provider must be explicitly compiled as 32-bit application
example, since the Visual Studio default as target CPU "Any CPU "has to be switched here on x86 (see figure).
After I had the mistake pinpointed and fixed (if one in this case, so to speak), were my eyes but even greater.
The beloved, Microsoft.Jet.OLEDB.4.0' provider supports namely no 64-bit. And this is not planned in the future to change!
So what can you do?
It's simple:. Applications that use this provider must be explicitly compiled as 32-bit application
example, since the Visual Studio default as target CPU "Any CPU "has to be switched here on x86 (see figure).
0 comments:
Post a Comment