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?
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.
I recently installed the Office 2016 32 bit edition on my Windows 10 Enterprise OS.
I had a Story Board Add-In with PowerPoint - Office 2013, which now does not work.
I can see the Add-In but when I click any of its menu items, I get this message:
TF86001: Team Foundation was unable to load the Office Add-In. This
may be caused by a Team Foundation Client installation problem or lack
of .Net programmability Support in the Office Application.
For more information, see the following Microsoft website:
http://go.microsoft.com/fwlink/?LinkId=220459.
So far I have tried the following steps:
- Reinstalled Office
- Repaired Visual Studio 2015 Enterprise Edition
- Reinstalled "Microsoft Visual Studio 2010 Tools for Office Runtime (x64)" from https://www.microsoft.com/en-us/download/confirmation.aspx?id=48217
My suspicion is that since I have a 32 bit version of Office 2016 on my 64 bit OS, I would need a corresponding 32 bit version of Visual Studio Tools for Office. I was able to download the 32 bit edition of the software but it was blocked from being installed by the OS.
Any suggestions? Hate that storyboard no longer works :-(
Finally found the solution.
As I suspected, I had to first remove all 32 bit editions of Office, including Office Pro, Visio & SharePoint Designer.
Then I installed Office 64 bit edition.
Went into File, Options, Add-Ins, Manage COM Addins.
Added "Team Foundation Add-in" and bingo the Storyboard menu came back
Click on "Storyboard Shapes" now works perfectly!
Some Explanation
It worked inb the Office 2013 32 bit version because Visual Studio Tools for Office allowed a 32 bit install. Since I installed the new version, VSTO ONLY allows the 64 version to be installed, i.e. it auto-detects your processor in the one installer file. Hence everything now has to be the 64 bit edition.
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 ..
Running VS 2010 under Win7 64-bit, and have Office 2010 installed. The application I'm working on opens and searches Excel spreadsheets and needs to run under Vista 32-bit with Office 2007.
I've tried the suggestion found here - drop Microsoft.Office.Interop.Excel v14 and add v12 - but running o2007pia.msi just tells me I have to install Office 2007. I don't have Office 2007 available to me, and I can't install anything on the machines running Office 2007.
Is there a way around this?
o2007pia.msi is not forward-compatible with Office 2010. Use the Office 2010 PIA, which should be backward-compatible with Office 2007, so long as you don't use any Office 2010 specific features.
Does anyone know if there is a way to make an Excel 2003 Document Level Customization work with Excel 2010? When I try to execute this document level customization built on Excel 2003 and VSTO 2005 SE, I get the following error.
"The assembly * could not be found at or could not be loaded.
You can still edit and save the document. Contact your administrator or the author of this document for further assistance."
Any help would be appriciated.
Just to share with people what I've learned thus far.
Office 2010, specifically in this case Excel 2010, has 64bit compatibility issues with Document Level customizations and I think Add-Ins when executing solutions built on Excel 2003 files. This appears to be an issue more specifically with Visual Studio Tools For Office SE (VSTO) where the OTKLoader.dll, being 32 bit, can't be loaded by Excel 2010 64bit version.
Our specific test was to take an Excel 2003 Document Level customization built by Visual Studio 2008, and install it on a Windows 7 64 bit machine running Office 2010 64 bit. The error received is the error as stated in my original question.
We then took a Windows 7 64 bit machine running Office 2010 32 bit and installed the Office Business Application. The OBA, the documen level customization, executed without error.
You'll probably want to reference the following article from Microsoft.
"Compatibility Between the 32-bit and 64-bit Versions of Office 2010"
http://msdn.microsoft.com/en-us/library/ee691831.aspx
I personally haven't made it through the article completely, but there's enough descriptive text and some explict statements that lead me to believe that Office 2003 customizations, currently, are not compatible with Office 2010's 64 bit version.
Hope that helps someone out there. This was a real pain to sort out.
Note the options we're presenting at this time are to:
A: Only allow 32 bit versions of Office 2010.
B: All Office / Excel 2003 Document Level Customizations must be upgraded, at a minimum, to Excel 2007 solutions.
No you cant, because interop/vsto library you reference has to be different.
Excel 2003 works on VSTO 2005 SE whereas Excel 2010 needs VSTO 2010 library.
VSTO 2005 doesnt work with Excel 2010 and VSTO 2010 doesnot works Excel 2003.
To expand on your findings, Rob, yes, that is correct (you can). I believe the other contributor has made a mistake.
For 32-bit versions of Office, it will work (and it does, so you have found), but it will not work for 64-bit editions of Office. Microsoft clearly states this compatibility restriction (well, as a footnote at least).
See the MSDN article Running Solutions in Different Versions of Microsoft Office.
Under section "Running Office Solutions Created By Using Previous Versions of Visual Studio", you will see in the chart in the last row that using VSTO 2005 SE with a project template targeted for Office 2003 will run on Microsoft Office 2003, Microsoft Office 2007, and Microsoft Office 2010 (32-bit only).
It goes on further to say that you will be required to install the Visual Studio 2005 Tools for Office Second Edition runtime on the client's PC.
Your options that you described are correct. Those should be the only options that you have.