I am working on Visual Basics using Visual Studio 2008, my application is to read the data from the Microsoft Access database and plot the graph using Crystal Reports.
For accessing to database I need to use a method:
conn.ConnectionString = #"Provider=Microsoft.Jet.OLEDB.4.0;Data source=D:\a.mdb";
Which is working fine in 32-bit machine but i try to run it on 64-bit machine I am getting the error:
Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
So can any one help me out how to resolve this? I need it run it on 64-bit.
Download the Access 64 bit redistributable from here.
After you install it, you can use Provider=Microsoft.ACE.OLEDB.12.0 for this version of 64 bit OLEDB.
In your project properties → Build, change your "Platform target" to x86, then it will find the 32 bit driver.
Related
I have a program (.Net Framework 4.6) that reads and updates excel spreadsheet via OleDd.
I have ported this code to .Net 6 solution using the System.Data.OleDb (6.0.0) package.
It works fine on my development pc (Win 10), but when I upload it to deployment server (Windows server 2016) I get error:
The data providers require Microsoft Data Access Components (MDAC).
Please install Microsoft Data Access Components (MDAC) version 2.6 or
later.
The .Net Framework 4.6 app is working on the deployment server just fine.
I have installed:
AccessDatabaseEngine2016.exe
mdac28sdk.msi
My .Net 6 app is running in 32Bit mode
What am I missing?
Regarding a .NET_6 project I'm working on under 64bit Visual Studio with C#, and which I was in_serious trouble with, well, reading your question text brought me to rebuild this project of mine now specifically for 32-bit instead of building for "Any". This solved my_pending problem to get OLE.DB successfully opening a_connection to M$Access, which had been installed as part of 32-bit M$Office. It was a relief to finally get across my OLE.DB hurdle this way (after a good number of hours), but in hindsight I am surprised that earlier on, with .Net Framework v4.8, I can't seem to have needed this sort of bitwise accuracy.
So for what it's worth, at least in my case bitlevels were essential and crucial to get OLE.DB working under .NET_6.
I am trying to connect to a server in PowerPivot. I am running across a few problems. Here is the connection string:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\accounting001\Accounting\TimeSlips2014\Databases\Philadelphia\;Extended Properties=Paradox 5.x.
It uses NT authentication as the password. I have read all about the problems with MS Jet 4.0. I am running 64x on 64x office apps. I receive the not registered on local computer error. Can anyone help me connect. I already installed the Access 2010 DB engine however I wasn't able to get it to connect. Thanks!
The Microsoft OLE DB Provider for Jet and the Jet ODBC driver are available in 32-bit versions only. You can't run them in 64 bit mode.
The Solution
If you run a program in a 64 bit environment and need to utilize jet to open an Access, Excel or text file there are several options to make this work.
Run the program in WoW64 mode (emulates 32-bit on 64 bit systems). This will make the 32 bit drivers work.
If the application is an web app hosted on IIS 7 you can choose to configure the web sites application pool to run in 32-bit mode.
With Office 2010, there are new drivers, the 2010 Office System Driver, which will be provided in both 32-bit and 64-bit versions. You can use these drivers to let your application connect to Access, Excel and text files in a 64 bit environment utilizing the new 64-bit drivers. The provider name is "Microsoft.ACE.OLEDB.12.0". You don't need to buy or install the Office suite, the components are available as a separate download. http://www.microsoft.com/downloads/details.aspx?FamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
Summary
It is possible to open Excel, Access and text files on 64 bit systems. You can either configure your app to go 32-bit or you can change your application to use the new 64 bit drivers.
See the original link for this information here.
I just downloaded the Delphi 2010 iso from my SA-subscription and wanted to install it in addition to my other Delphi installations on my notebook computer. Unfortunately it refuses to install because the machine is running Windows 2000.
Is it possible somehow to get it to install it anyway? Or is there a technical reason why it might not work, even if it installed?
edit:
Some more information:
Delphi 2009 installed fine on that computer, so dotNET 2.0 is already installed.
The Delphi 2010 installer comes up, asks me for the language to use and then says "This product requires at least Windows XP. Setup cannot continue."
What I am looking for now, is either:
a way to get the installer to skip this check and install anyway - or -
a reason why this would not work (e.g. Delphi is using some Windows API that is not available in Windows 2000)
You could try to start the setup.exe with the /Win2K parameter. Maybe this helps. But I heard from a German forum that a user who installed Delphi 2010 into Windows 2000 had lots of problems with the IDE. So use the /Win2K parameter at your own risk.
And you must have at least .NET 2.0 SP1 installed
According to the minimum system requirements, Windows 2000 is not supported. They might use some XP+ specific API's these days, but then again they might not, as Delphi 2009 installed fine on Windows 2000.
The first thing you might want to check is if you have .Net (2.0 minimum) on your machine. According to the document linked above, they try to install The .Net 3.5 distributable otherwise, and that one definitely requires XP minimum.
windows 2000 is supported in Delphi 2010, check the following link:
Target Windows 2000, XP, Vista, and Windows 7 from single source
I think the problem is from your pc, maybe because there are other versions are installed, can you post the message?
I developed a Windows service which is running without any problem in Windows XP service pack 3. When I deployed this service in Windows Server 2008 it is not working. The service started without any problem.
I enabled the option Windows XP service pack 2 from the compatibility property of the .exe which deployed there.
But no more action after the starting the service.
What could be the problem?
One thing I would check it to see if any of your referenced assemblies are 32bit specific. We ran into a similar problem when using Microsoft SQL Server Reporting Services. The .dll we used to get a list of the web service interfaces, was 32bit/64bit specific, so we had to swap it out depending on which envionment we were running on.
Since the error could hide anywhere I would suggest to first discern what exactly is not working under Windows Server 2008.
Implement some logging functionality into your service (if you didn't do so already, I strongly recommend it) and let the result be printed into a log file. See what's working and when it stops to work. Hopefully this will give you a better understanding of what's going on under the hood.
Also, this way we can help you way better than now.
[EDIT]
Maybe these two can help you?
COM Class Factory Error
Running 32 bit app using 32 bit com on a 64 bit Windows machine
What is the best way to setup Microsoft Robotics Studio 2.0 on 64 bit Windows Vista? Appearently something needs to be done beyond the default installation to get it to run properly.
Microsoft has released Microsoft Robotics Developer Studio 2008 R3 which includes 64 bit support out of the box, no special install required. It also supports Visual Studio 2010.
According to MRDS requirements Windows 7 is the best OS to run MRDS. If you use Vista, there are high possibilities to find it difficult to run RDS. read more here and here