I have an application made using Visual studio 2008 and it uses a Microsoft access 2007 file as back end database(file). it works well on my laptop running windows 7 64 bit. but I get an error when I install and try to run it on my PC running windowsxp and Office2000. the error is" Microsoft oledb12.0 not registered on your machine".
how can i run the application on my PC ?
"Microsoft oledb12.0 not registered on your machine"
how can i run the application on my PC ?
Since you used MS Access 2007 DB as back end then you should install at least MS Office 2007 or later on your PC ..
Related
I just received a new Dell XPS tablet with Windows 10 Pro version 1909 I have also have:
one other Windows 10 XPS tablet (last year's model)
Windows 7 Inspiron
Surface Pro Windows 10 version 1903
My Access 2007 with Word 2007 automation runs flawlessly on the other machines, but on the new machine, I am getting an error with this line:
Set objWord = New Word.Application
The error states
"Automation Error - Library not registered." Error 8002801d
There is a proper reference checked for Word Object Library 12.0 pointing to:
C:\PROGRAM FILES (x86)\Microsoft Office\Office12\MSWORD.OLB
The new machine has all the latest updates, and the Office 2007 has been installed, repaired, etc. The Database has been recompiled, repaired, compacted, etc. There seems to be no way to register a .OLB file
My database application runs fine if I take out any attempt to open a Word document, and the Word 2007 program also works fine independently. It's just the one line that's the problem: Access simply doesn't recognize Word even though there is a proper reference.
Since the application is working fine on three other computers. What am I missing? This machine is under warranty with Dell for Premium support, but I don't see how this can be a problem with the computer because it is otherwise working well.
Problem: I can't open the installed program on other computers.
I created a program on visual studio 2010 with database created on sql server 2008 express. When i created the setup and install it on MY OWN PC, it runs properly together with its database. When i try to install it on other computers, it successfully installed but i cant open. When in double click the shortcut, even the .exe, it is not responding. The application is not opening/running.
Any ideas?
Your application is probably trying to connect to a database that doesn't exist. You'll need to install SQL Express on the computer where you installed the software.
I have developed a desktop application in vb.net using visual - studio 2010.
I want to run that application in different pc every time. For that I have created a build of that application.
But I am not able to run this application other than my pc.
I also installed the dot net framework 4.0 in other pc but it gives error "WIC component not installed".
What should I do to run my application in different computer systems every time? , what are the pr-requisites for running the application.?
Please help. Thanks in advance.
Googling that error would seem to suggest you need to install the Windows Imaging Components on the other machines.
64 bit downloads
32 bit downloads
Judging the by the system requirements I'm guessing Windows 7 onwards includes this by default.
Supported Operating Systems: Windows Server 2003
Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
Windows Server 2003 R2 Standard Edition (32-bit x86)
Windows XP Service Pack 2 Windows XP SP2 Windows
Server 2003
I have done document imaging on windows 7 with MODI in office 2007 and it is successful. But when I install the same office 2007 with MODI onto windows server 2008, it does not work with my program anymore. it is throwing a comexception of "(0xc6c80001): Object hasn't been initialized and can't be used yet at MODI.IDocument.OCR". I did not change anything for the codes at all. Anyone has any idea?
I am bit confused as on this..
Which version of Share Point designer (32 or 64bit) do I need to use to work on SP 2010.
When I try to download the 64 bit , I see a message as "32 bit is recomended for most users ..".
I have installed SP 2010 on win 2008 R2 in virtual box. Is it mandatory for me to install Vs 2010 on same machine to develop web parts ...?? Can I install Vs 2010 in a different machine ..?? Which version of VS 2010(Express, Prof, Prem or Ult) is required ..??
Sharepoint 2010 can be installed on client machines with Windows 7 or Vista.
It is required for Sharepoint 2010 products that you are running x64 version of OS.
The development tools like VS and Sharepoint designer can be either 32bit or 64bit.
Microsoft recommends 32-bit for all the Office products, including SharePoint Designer included. I believe it's mostly to do with compatibility with other programs.
"The 32-bit version of Office 2010 is the recommended option for most people, because it prevents potential compatibility issues with other 32-bit applications, specifically third-party add-ins that are available only for 32-bit operating systems."
Taken from here: http://office.microsoft.com/en-us/sharepoint-designer-help/choose-the-32-bit-or-64-bit-version-of-microsoft-office-HA010369476.aspx
Which version of Share Point designer (32 or 64bit) do I need to use to work on SP 2010?
You can use both the 32-bit or the 64-bit version. But, it is recommended that you install the 32-bit version because the Office 2010 32-bit version is recommended. If you install the SharePoint Designer 2010 64-bit version than you cannot install the 32-bit version of Office 2010.
I have installed SP 2010 on win 2008 R2 in virtual box. Is it mandatory for me to install Vs 2010 on same machine to develop web parts ...?? Can I install Vs 2010 in a different machine ..?? Which version of VS 2010(Express, Prof, Prem or Ult) is required ..??
I have also installed SP 2010 on Win 2008 R2 in VBox. The SP installation is a standalone installation. I have also installed VS 2010 on the same VM. But, you could separate out the SP and VS 2010 installation on multiple VMs. The downside is you will need to have both VMs running at the same time (at least during your deployment to SP). You will need at least the professional edition of VS 2010.