BrioQry dll error in Excel 2003 VBA6.5

Hi,
I use Hyperion - Explorer 8.3.2.152 Windows XP, Update Version SP3.
Under VBA 6.3 the following code runs well in Excel 2003:
Sub testBrio()
Dim bqy As BrioQry.Application
Set bqy = New BrioQry.Application
MsgBox "works!"
Set bqy = Nothing
End Sub
After updating to VBA 6.5 an error is triggered when creating the application object - error 430: Class does not support automation.
Does anyone have any idea how to solve this issue?
Thanks!

Hello Nicolas,
Please post this query to the [Legacy Products|SAP BusinessObjects BI Legacy Products; forum.
That forum is dedicated to topics related to legacy products such as Business Objects Enterprise 5.x and 6.x.
The forum is monitored by qualified technicians and you will get a faster response there.
Also, all Legacy Product queries remain in one place and thus can be easily searched in one place.
Thanks a lot,
Falk

Similar Messages

Need help for "Numeric field Overflow" error in excel 2003.

Hello,
a friend of mine have a problem exporting Business Objects 5.1.8 to excel 2003 (turning on windows 2000).
Each time she want to export her reporting in excel format (.XLS), she obtain a "Numeric field Overflow (3349)" error.
So, she export in .CSV format, but it's not easy to use for her following tasks.
What could she do ?
Does she do an "update" to newer version of B.O., or there are a solution at her problem ??
Thanks in advance.
Nicolas
P.S.: I searched for solution on this forum, but found nothing.
Edited by: Nicolas Kowarski on Sep 28, 2008 10:16 PM

Hello Nicolas,
Please post this query to the [Legacy Products|SAP BusinessObjects BI Legacy Products; forum.
That forum is dedicated to topics related to legacy products such as Business Objects Enterprise 5.x and 6.x.
The forum is monitored by qualified technicians and you will get a faster response there.
Also, all Legacy Product queries remain in one place and thus can be easily searched in one place.
Thanks a lot,
Falk

Oidldapd.exe oracore9.dll error in windows 2003

Hi,
i am using OID 9.0.4.0.0 , in a windows 2003 enterprise server (machine is a compaq proliant dl580 g2)
i'm gettin the following error in event viewer:
Reporting queued error: faulting application oidldapd.exe, version 0.0.0.0, faulting module oracore9.dll, version 0.0.0.0, fault address 0x000193a7.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
any help ?
Thanks
Rui Madaleno

Hi there,
I am just wondering if you resolved the issue.
If yes, could you please send me the information to [email protected]
thanks in advance,

Crystal 8.5 Export to Excel 2003 Error after Excel SP3 install

Post Author: tecboy
CA Forum: Exporting
Just upgraded Office 2003 to SP3. When exporting a Crystal 8.5 report to Excel 2003..I now receive an error message...file error data may have been lost crystal...i click ok then the Excel spreadsheet opens. all the data appears to be there. I have tried switching between extented and not and also tried switching between application and disk file...same results...SP3 for Office changed something...Just trying to determine what i need to correct to make this error go away...

Post Author: tecboy
CA Forum: Exporting
Yes and no.....I replaced the export dll for Excel with a newer one...the newer dll removed the error message but the layout of the exported crystal reports was screwed up...so i went back to older version. I think it may have something to do with the default speadsheet or tab name that Crystal Reports creates that SP3 for Excel doesnt like...If i recall...i ran into something similar when i was on Crystal 7 and upgrade to Office 2003....

Smartview 11.1.2 & Excel 2003 SP3-Replace All Error

My client has Smartivew 11.1.2 with Excel 2003 and is doing a private connection to an Essbase cube for ad-hoc analysis. All comes back fine but client does the Excel replace-all functionality and it throws the "Smartview handled an unknown exception thrown by Microsoft Office"....client can hit ok and the replace-all works but not sure why we get the error. This issue is not happening with Excel 2007...anyone see this? Thanks so much!
Edited by: 895068 on Nov 4, 2011 6:28 AM
Edited by: 895068 on Nov 4, 2011 6:28 AM

Hi,
thanks for your answers. From all I could find out from Oracle support, I'll have to wait until 11.1.2.1 is GA and then try again :-(
Or will there be a patch for 11.1.2.0 as well?
Best regards,
Markus

Error when opening XLSX file with Excel 2003 SP3, file does open but in read only mode with temporary name

I am using Excel 2003 SP3 and have the Office 2007 compatibility pack installed. When I open Office 2007 formatted Excel files (XSLX) directly in Windows Explorer, I receive the following error if I do not have Excel already opened:
"Windows cannot find '<path to file>'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search."
Even though I receive the error, the file does open; however, it opens in Read Only mode with a name such as "Xl0000024.xls". The number seems to increment up each time it happens.
Now here is the strange part. If I have Excel already open and try to open the file in Windows Explorer, the file opens fine in Modify mode with no error and with the correct file name.
I Googled the error I was getting and found KB211494. It says I should uncheck the box in Options on the General tab that says "Ignore other applications", but this box is already unchecked in my case. Any other ideas? This is
really frustrating as a small percentage of our company has upgraded to Office 2007 with the rest still on Office 2003.

This may be a file association problem. To solve that:
In Windows 7:
1. Right-click the file,
2. Select "Open With"
select [Your Program Here]
3. Check always use this program.
In Windows XP:
1. Locate the file as you have described above
2. Right click the file
3. Select Open with from the pop-up menu
4. Click Choose default program…
5. Select Excel in the Recommended Programs box
6. Check Always use the selected program to open this kind of file
7. Click on OK.
1. Make Excel not available from Office 2007 listed under Programs and Features in Control Panel.
2. Take a registry backup using the steps given here
3. In the registry editor window expand HKEY_CLASSES_ROOT and navigate to .xls right and delete it.
4. Exit Registry Editor
5. Undo Step 1 to make Excel available.
6. Restart the computer and verify it the issue is fixed.
If this answer solves your problem, please check Mark as Answered. If this answer helps, please click the Vote as Helpful button. Cheers, Shane Devenshire

Error message in excel 2003 : compile error in hidden module could be caused by Adobe Acroate add in

The error message in excel 2003 : "compile error in hidden module AutoExecNew" could be caused by Adobe Acroate add ins, thats waht microsoft told me.I use windows xp service pack3.I have got reader newest version and photoshop 6.0. With this and also with an older reader version I got the error message when opening excel. what can I do?
Best regards Ray

If you have Adobe Reader, you (probably) don't have Adobe Acrobat, a
commercial ($$) product. 5.0 is a very old release.
But you can check if the files are there anyway from long ago. See
http://support.microsoft.com/kb/307410
Aandi Inston

Opening an Excel 2003 file in Office 2010 Universal Data Connection error when opening the file from a domain.

Hi.
One of my users are having problem with old accounting files in Excel 2003 when opening Excel 2010.
The user experience that linked information is not being updated properly.
And suspects that it something do with Universal Data Connection .
How can an Excel 2003 spread sheet be converted to Excel 2010 spread sheet and still contain active links?
When the user is opening and converting the file as mention in your suggestion, on the common share on a common domain, the links "breaks".
we are not using SharePoint on our domain.
But when doing it on a local machine, the links does not "breaks".
Looking forward to get solved to this problem.
Thank you in advance.
Rgds

it sounds link, the links changed from relative paths to absolute path. You need to use absolute path in original file.
KR

Acrobat 9.0 PDFConverter toolbar missing in Excel 2003

For some reason the PDFConverter toolbar disappeared in my installation of Excel 2003. I remember an error message flashing up but apparently I didn't pay enough attention. That happens all to often unfortunately.
After an hour of searching several websites, including these adobe forums, I found a procedure that was written for Acrobat 7.0 but it also solved my problem with Acrobat 9.0. I added this thread in the forums with the intent of making it easier to find for the next person.
The answer I found is response #2 in this thread - http://forums.adobe.com/message/2152995
The question that began the thread is "Acrobat 7.0 Missing PDFMaker files and won't pdf files"
The answer was posted by user J.O.S. on August 4, 2009
The answer she/wrote is:
I have had this problem with nearly every version of Adobe Acrobat up to and including 9.0
Here are four things I do to resolve this issue in order of time/difficulty:
First, I made sure that the Adobe Acrobat plug-in wasn't disabled.
In any Microsoft Product such was Word, Excel, etc. go to Help>About Microsoft (Word/project, etc) and then click on the 'disabled items' button.
If the plug-in is disabled, select it and enable it again.
Second, I make sure the PDFMaker files are registered.
I open a command prompt and navigate to the PDFMaker plug-in dll files in Adobe.
In Adobe Acrobat 8.0 the file path is:
C:\Program Files\Adobe\Acrobat 8.0\PDFMaker\Office
I then type in:
regsvr32 PDFMOffceAddin.dll
That should enable the Office PDFMaker plug-ins.
Third, I make sure that the AcroDist.exe application path was configured properly in the registry.
If it isn't, I just create it.
Registry path:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths
Look for the entry "AcroDist.exe"
If not there, create it - it is a 'Key". (right click on App Paths and choose New>Key)
In the AcroDist.exe key the (Default) value should be:
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\AcroDist.exe
or
C:\Program Files\Adobe\Acrobat 8.0\Acrobat\AcroDist.exe
depending on which version of Adobe Acrobat you have. Essentially you put the absolute path for the AcroDist.exe file in there.
The only other entry in the AcroDist.exe key should be the String Value Path. If it isn't there, create it (right click and choose New>String Value)
The name of the String Value should be Path and the value should be the path of the AcroDist executable. e.g.:
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\
or
C:\Program Files\Adobe\Acrobat 8.0\Acrobat\
Close out the registry and try to use the PDFMaker again
If that still doesn't work then I run a repair on Adobe. If THAT doesn't work then I completely uninstall/reinstall.

In Adobe acrobat pro, go to the Edit/Preferences menu and select the internet menu and make sure the Display PDF in browser item is checked.
Click the Internet settings button and go to the advanced tab and make sure the Enable third-party browser extensions is checked.
THen open the 32 bit version of IE9.

Excel 2003 Export fails with Diadem 8.10

We still use Diadem 8.10 on some test stands. These stands were just loaded
with the Office 2003 suite.
Since then, Diadem 8.10 cannot export our data to Excel. Everything seems
fine in Diadem. The export assistance appears to work as always.
When we try to open the exported file in Excel, we get this error:
> "The document is corrupt and cannot be opened. To try and repair it, use the Open and
> Repair command in the Open dialog (File menu) and select Extract Data when prompted.
Then Excel shows "Extracting Data from Export_Data.xls" in the status bar, with a progress control.
Eventually, Excel shows this error:
> Errors where detected in 'Export_Data.xls,' but Microsoft Office Excel was
> able to open the file by making the repairs listed below. Save the file
> to these repairs permanent.
>
> Damage to the file was so extensive that repairs were not possible. Excel
> attempted to recover your formulas and values, but some data may have
> been lost or corrupted.
The result is an Excel file with the correct name, but all cells are empty.
I have tried reinstalling Diadem 8.10, but the results are the same. I can install
Diadem 9.10, and Excel exports are perfect.
Unfortunately, the scripts for our application do not work in 9.10, so we must use
8.10 for a while yet.
Any ideas to fix the Excel export function for 8.10?

Hi jbrandim,
What happens if you take that Excel file created by DIAdem 8.1 and try to open it in an older version of Excel? Presumably this used to work fine for you prior to Excel 2003. Does it still? If it does still work, what happens if you then resave this imported Excel file with the older version of Excel. Can this new (resaved) Excel file be opened in Excel 2003?
The new Excel export code that is working correctly for you in DIAdem 9.1 will likely have trouble running in DIAdem 8.1. You could try replacing the "...DIAdem\AddInfo\gfsexcel.dll" in the DIAdem 8.1 directory with the new file from the DIAdem 9.1 directory, but there are no guarantees. You should save a backup version of the dll in case it doesn't work.
Brad Turpin
DIAdem Product Support Engineer
National Instruments

? Office 2013 to support Excel 2003 (XLS) spreadsheets containing VBA CommandBars references

Thanks in advance for reading this and offering any wisdom you have! I am not an expert in any of the following, so apologies if off base.
The basic problem is: I need to use Excel 2013 to support Excel 2003 (XLS) spreadsheets containing VBA 'CommandBars' references which don't seem to work in Excel 2013. Details below.
Most of our users are still using older desktop windows PCs and Office 2003! We are beginning to upgrade to laptops running Windows 8.1 with Office 2013. Of course, we IT technical people are using the new laptops first. These new laptops are
64 bit.
Years ago, someone did a lot of development with spreadsheets here in Excel 2003 file formats that automates many activities and routines. Now we with the new laptops are having to support this development using new machines.
There is a basic compatibility issue that appears when first opening these Excel 2003 files that have VBA code that I'll detail below; I seem able to get by that problem.
The current problem appears to be that the existing Excel 2003 VBA code has many references to: "For Each bar In Application.CommandBars". As I've learned, the Application.CommandBars VBA functionality is focused on older MS Office versions' menu
commands, but "...Starting from Office 2007 the Fluent UI is used instead." In other words, because MS Office isn't menu-driven beginning with version 2007 (uses 'the ribbon'), it appears that these references to: "For Each bar In Application.CommandBars"
create a basic incompatibility to opening these spreadsheets in Office 2013.
For a spreadsheet, after I resolve the issue detailed below and save it, when I reopen it I encounter error "Compile error: can't find project or library."
For example, the following code snippet:
Private Sub Workbook_Open()
For Each bar In Application.CommandBars
bar.Enabled = False
Next
results in: "Compile error: can't find project or library."
(Sorry, can't include images yet, I am not a VERIFIED USER of this forum yet.)
I went into VBE's menu: Tools>References and check for anything marked MISSING, which I deselected. But I am still receiving this error.
I don't want to get into changing the code a lot to support both Excel 2003 and 2013 (I am no VBA expert, just a dabbler).
And Microsoft officially says that Office 2003 is incompatible with Windows 8 although Application.CommandBars seem to be somewhat supported in Office 2013 .
Are you aware of a quick VBA workaround to get by this?
•I could comment out the validations, commands for: "For Each bar In Application.CommandBars" but then the spreadsheet code probably won't work for users using Office 2003.
Alternatives would be:
•Installing Office 2003 on my Win 8.1 64 bit laptop anyway, in spite of MS's saying incompatible, since this thread discusses at least one person has been able to use Office 2003
•Keeping one older PC with Office 2003 on it for us to support the old Office 2003 code until everyone upgrades their systems
Thanks
Basic compatibility issue that seems solvable:
Opening these spreadsheets displays this error:
Compile error:
The code in this project must be updated for use on 64-bit systems.
Please review and update Declare statements and then mark them with the PtrSafe attribute.
This seems resolvable by going into the VBA code and just adding element 'PtrSafe' where functions are declared; in other words, replacing VBA code "Declare Function" with "Declare PtrSafe Function" seems to get by this.

Hi Allan_L,
Please try the methods that provided above. And this is the forum to discuss questions and feedback for Microsoft Excel, your issue is related to Excel DEV, if you have further question, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Can not open Excel 2003 embedded worksheet in Office 2010

I have seen many similar issues to this but I think I have some unique factors that are making my issue a bit tougher to resolve. I have a user who has a word doc which he opens in Word 2010. This doc has several embedded excel sheets. When he tries to click
one of these embedded excel sheets to edit he gets an error: "the program used to create this object is excel the program is not installed on your computer". It will give an option to repair which we have tried but it makes no difference.
Some things to note that I think makes this case more unique than others I have googled.
This seems to be the case only with embedded excel 2003 spreedsheets. He can open newer excel 2010 spreedsheets that more more recently added to the file.
He previously had Office 2013 which we had to uninstall, and put Office 2010 on. This was done because of a piece of software this company uses that was not compatible with office 2013. (Personally I think this may be where the problem is as there seem to
be remnants of Office 15 in the registry.)
I have tried the standard fixes of Disabling the Com add-ins, running office repair, and trying to Convert the embedded spreedsheet to an Excel Binary. The convert failed and gave me a generic error about possibly not being allowed to save to the location
or needing more memory or space but none of these are the case.
I have not yet tried to uninstall office 2010 and reinstall and I am hoping that I won't have to. This issue just seems odd to me. Other users can edit these embedded spreedsheets fine which is why I think it has something to do with the fact that he downgraded
from 2013 to 2010.
Anyone of thoughts, ideas, suggestions? Thanks.

Hi,
I noticed that use newer excel 2010
spreadsheets that more more recently added to the file. Did you try to embed the Excel 2010 file to Word 2010 test? If it works fine, I suppose that it was a compatibility issue.
Because Excel 2010 had change the file format with Excel 2003.
I recommend you try to install Office 2010 sp2 and compatibility pack.
http://blogs.technet.com/b/office_resource_kit/archive/2013/07/31/download-the-new-microsoft-visio-compatibility-pack.aspx
https://support.microsoft.com/kb/923505/en-us
And there is a similar issue, we also could install the hotfix to test.
http://social.technet.microsoft.com/Forums/office/en-US/b0dc1e24-847d-44e9-95c5-f789a0d50047/cannot-edit-embedded-excels-after-closing-document?forum=officesetupdeployprevious
Regards,
George Zhao
TechNet Community Support

Error in Excel 2007.

We have a user who gets an error when he will start the BPC for Excel in Excel 2007. And he can not open the BPC for Excel. The following error message appears: "In order to open the file Ev4Excel.xla the file had to be repaired or it was forced to remove unredable materials. The workbook has lost its VBA projects, ActiveX controls and all other programming functions." And it can not open the BPC for Excel
The user also has Excel 2003 installed on his computer and if he uses Excel 2003, it works.
Is it possible to have both Excel 2003 and Excel 2007 installed on the same computer and run SAP BPC against both
Are there some Excel add-ins that you have to install when you install the Excel 2007?

Hi,
In SAP BPC installation guide you will find below recommendation
Note: In order for the software to function correctly in Excel 2007, you must
install the Microsoft.ACE.OLEDB.12.0 provider, which you can get from the
Microsoft website. The provider must be installed on the Application server.
This provided in 25mb in size. We installed it on our application server. but still some errors with excel 2007 is not resolved. Finally we tried with office 2003, but still error continued. When we moved back to office 2007, some excel-addins which were available earlier went missing.
regards,
Lokesh Nandula

BW error with Excel 2007

Hi Expert,
I found some critical issues that in Excel 2007
1,
can not read 20000 records at one time, it will pop upan issue window with the error message "Client out of memory" , but it works well in Excel 2003.
2,
When I tried to open the other report it pop up another error message "The program will now terminate Please refer to the trace for further infomation",but it works well in Excel 2003.
Are there any experts can give some suggestions ?
Len

Hi
please refer teh following notes : 1260213, 1242583, 1052761 1175947.
Regards, Hyma

Problem with solver DLL load and Excel 2010

Since upgrading from Office 2007 to Office 2010 we've started to experience a problem with the solver addin when our own analytics addins is also loaded. I have found a solution, but I think it may highlight a problem with the latest version of the solver
addin for Excel 2010.
Firstly, to describe the problem - the solver addin seems to load normally when Excel 2010 starts up, however when a "Solve" is performed we are seeing a "File not found: Solver32.dll" error at the final "Keep Solver Solution" stage. This only happens our
own analytics addin is loaded. We've been careful to make sure that our own addin does not change the working directory and also that it has been built against the correct Excel 2010 SDK libraries. We do not see this error with any other versions of Excel
running on the same PC or any other environment.
After some searching we found other people were having similar problems and after a bit more probing I found a solution that works - but that I'm not very happy with.
If I copy the Solver32.dll from:
C:\Program Files (x86)\Microsoft Office\Office14\Library\SOLVER
(where it was installed)
into :
C:\Windows\SysWOW64
(where Windows 7 keeps its 32 bit system DLLs)
then the problem goes away.
This seems to indicate that somehow Office 2010 has a problem that causes it to search in the wrong folder for the Solver32.dll when another addin is loaded in between the original Solver32.XLAM at start up and the use of the Solver in the sheet (which eventually
requires this DLL to be loaded). Oddly, this only happens after a solution is found and "Keep Solver Solution" is selected - and I'm not sure why it's not looking for Solver32.dll any earlier.
This is not a problem with any earlier versions of Excel and I suspect is a bug in the Office14/LIBRARY/SOLVER implementation. Is there any way to get this followed up?
Thanks,
Andy

I'm facing the same issue. With an Excel VSTO add-in we're building. When the add-in is enabled the assembly solver32.dll can't be found. With our add-in disabled the DLL is resolved as (Sysinternals Process Monitor trace):
EXCEL.EXE CreateFile
C:\Program Files (x86)\Microsoft Office\Office14\Solver32.dll
EXCEL.EXE CreateFile
C:\Windows\SysWOW64\Solver32.dll
EXCEL.EXE CreateFile
C:\Windows\system\Solver32.dll
EXCEL.EXE CreateFile
C:\Windows\Solver32.dll
EXCEL.EXE CreateFile
C:\Program Files (x86)\Microsoft Office\Office14\Library\SOLVER\SOLVER32.DLL
and with our add-in enabled the following locations are tried, but solver32.dll won't be found:
excel.exe CreateFile
C:\Program Files (x86)\Microsoft Office\Office14\Solver32.dll
excel.exe CreateFile
C:\ArcGIS\______path to our add-in install location_____________\Solver32.dll
excel.exe CreateFile
C:\Windows\SysWOW64\Solver32.dll
excel.exe CreateFile
C:\Windows\system\Solver32.dll
excel.exe CreateFile
C:\Windows\Solver32.dll
excel.exe CreateFile
C:\Program Files\Common Files\Microsoft Shared\Windows Live\Solver32.dll
excel.exe CreateFile
C:\Program Files (x86)\Common Files\microsoft shared\Windows Live\Solver32.dll
excel.exe CreateFile
C:\Windows\SysWOW64\Solver32.dll
excel.exe CreateFile
C:\Windows\Solver32.dll
excel.exe CreateFile
C:\Windows\SysWOW64\wbem\Solver32.dll
etc...

BrioQry dll error in Excel 2003 VBA6.5

Similar Messages

Maybe you are looking for