I'm not an experienced vba programmer and working with access is not my cup of tea. I've been asked to fix some errors in an MS Access 2010 VB application. The sole user previously ran the application on a 32-bit platform but now has migrated to 64-bit. This caused the aplication to break. I have made some progress but every issue I resolve another seems to appear.
The following piece of code
DoCmd.OutputTo acOutputReport, "rptQLDExport", acFormatRTF, frm.txtDirectory.Value + "\QLD\All\QDATA.DOC"
is causing a runtime error 2587: Microsoft Access can't complete the Output operation
I have seached on the net for an answer but to no avail.
My development environment is Windows 7 SP1 (64-bit) and the application is running in Access 2010 (vba7, 64-bit). I'm willing answer questions to provide more information. Any suggestion will be appreciated.
This forum post suggests it is related to runtime versus full versions of Access (or Office). The suggested solution is to Copy the file UTILITY.ACCDA from the ACCWIZ directory to the same directory as MSACCESS.EXE
You would need to check licensing before distributing the file in your application installer, obviously.
Update: On a machine that fails, copy over ProcessMonitor (from technet; no install required). Filter to your application. Repeat the process and get it to fail. Examine the files that your application is trying to access and why they fail.
Related
I have a VBA file that is working fine on 10 PC's. VBA is hosted within a drafting package called MicroStation / PowerDraft. On 2 more computers when setting up the files as normal i run into an error which says
License information for this component not found. You do not have an appropriate license to use this functionality in the design environment
When checking through the VBA project i cant find any reference as to which file is causing the issue but also how to fix it? I have found a few articles on here and through Google which all direct to a Microsoft support page that is now a dead link. Can anyone help? All PC's are the same, Windows 10 64 Bit, same version of MicroStation, same Software and all Windows Updates up to date. The Files being referenced are below. They are all located and registered.
mscomctl.ocx
comdlg32.ocx
ieframe.dll
stdole2.tlb
msado27.tlb
Plus some more that i cant file the filename of.
Microsoft Forms 2.0 Object Library
Adobe Acrobat Browser Control Type Library 1.0
Microsoft Office 16.0 Access database engine object Library
Any help would be greatly appreciated!!
7 days late so you should have resolved this but if not or in case others are looking
Many reasons that message is raised partly to do with UAC level at install time and the mixed ages of MSoffice components. The root problem is possibly a missing OFFICE registry value the cause is described here https://learn.microsoft.com/en-us/office/vba/language/reference/user-interface-help/license-information-for-this-component-not-found-you-don-t-have-an-appropriate-l
but for MicroStation you must during install be using the correct "pre-requisites" so check the related versions of product and requisite
some potential "fixes" are described here Getting VB6 to reveal which component doesn't have a design time license installed but links are old eg they should lead to say http://support.microsoft.com/kb/195353/en-us
1.Q194751 FILE: VB6Cli.exe Fixes License Problems with Visual Basic 6.0
2.Q195353 FILE: VBUSC.EXE Provides Licensing for Discontinued Controls
these have solved the issue for some users as described here https://communities.bentley.com/products/building/building_analysis___design/f/aecosim-speedikon-forum/96029/install-aecosim
I found vbusc at this link which running as admin on x64 gave a positive update message however as I'm no longer running a VB enhanced PowerDraft can't confirm it solves this issue.
An amateur programmer has made a nice little program that works through VBA on top of a MS-Access2010 database. We are asked to make an installer for this database+VBA project. The code runs fine on any computer with Office installed, but on computers without Office we get the error above. On computers without office we install the MS-Access2010 Runtime, which is free, in order to be able to open the .accde file at all. But this does not prevent the VBA error.
I did some research on the issue but did not find anything related to this specific scenario. How can this be troubleshooted?
The problem was a version mismatch between the .accde file (sp1) and the installed ms access 2010 runtime (original) After upgrading the runtime to sp1 all was fine.
I'm using the Crystal Report 10 viewer ActiveX control in an Access App I've written. Works great in Office 2003 on 32bit versions of Windows. The problem arrises when I try to run the program in 64 bit Windows (with 32bit Office). I get the following error:
Run-time error '429': ActiveX component can't create object
I get this error on the following line of my VBA code.
Set rdApp = CreateObject("Crystalruntime.application.10")
How can I get this to work in 64bit?
I don't have any specific experience with Crystal Report, but I do have some experience with installing components on a 64-bit Windows environment that were intended for 32-bit Windows, so here are some general suggestions of things to try:
Before installing, try loosening the security privileges - I have Windows Server 2008; on this OS, they're under Start | Administrative Tools | Local Security Policy. Many old installers are thwarted by these controls. You'll want to return them to their defaults after the install.
Make sure that you run the installer with admin privileges (right-click; run as Administrator).
Examine the installation log for Crystal Report - it may indicate a failure registering a component. In one instance, I was able to get the installation working by running the command to register the failed component manually, on an administrator-privileged command line (the command was in the log).
If acceptable, try to create a Windows Virtual Machine running a virtual Windows XP, and try the installations there (this might be a bit tedious, due to your need for MS Office).
Take a look at VMWare's ThinApp - this is intended for packaging applications for administrators, but this was the solution we ended up using to shield one of our 32-bit apps from Windows 64-bit perils
Hope this helps; we struggled for awhile trying different things to get our legacy apps working on a 64-bit environment.
I am working on a dashboard related project using the MS BI stack integrated with SharePoint. I have a configured POC server running on Windows Server 2008 R2, SQL 2012 and SharePoint 2010. I am trying to run one of the MS tutorials that I have already completed on the MS virtual labs in a completely 2008 environment but doing so within my SQL 2012 / SharePoint 2010 environment and this requires I use the .dep file to set the tutorial up. When I first tried to run it I got the windows doesn't know which program to run it with but since the server is in a sandboxed area without net access it cannot search the web for the correct program. In the tutorial it mentioned the file ran via the command prompt so I tried opening it with that and unfortunately nothing happened, but I forgot to untick the always associate box so basically I now have two issues.
First is getting the .dep file back to having no default associated program to run with or finding out what actually is the correct one and the second is to actually get the required files I need to run the .dep file and set-up the environment for the tutorial. Unfortunately MS does not have a nicely detailed list on this.
I have tried using GPMC.MMC to remove the file association but as it is connected to our active directory the default features do not match up with what the technet article states on doing this and I don't want to cause errors on our active directory. Any advice on how to get this working would be appreciated.
You can try downloading the offline training kit.
This training kit should contain a folder with the name "assets". Into this folder you can find an installation of the software "DependencyChecker.msi". Just do this installation. The installation associates the .dep files with the "Dependency Checker Tool"
Secondarily, you can google around to find "How to install the Microsoft Dependency Checker Tool".
In the next link Microsoft talks about the tool.
http://msdn.microsoft.com/en-us/identitytrainingcourse_silverligthandidentity2010.aspx
For the visual folks:
And at line 61:
Everything I'm finding on the web is one of 3 solutions for the problem:
The user is trying to use an interop assembly without Excel installed. I have M$ office pro 2010 installed. So that's not the issue.
I'm not typing it out but you can look here
Users are running the interop assembly in 64-bit, I'm on a 32 bit machine. So that's unrelated. But I did try compiling as 32bit only instead of Any CPU. Didn't help.
Basically fix #2 is for those running this code on a server and their code is executing under the ASP user account, in my case its a desktop app so this should be unrelated but in desperation I added "Everyone" to the permissions and gave them all privileges. Didn't work.
So now I'm turning to here. Any questions, comments, concerns?