API to control Excel 2003

Hi,
I'm looking for an API to control Microsoft Excel 2003.
I tried to use the JExcel API an POI without real success.
Is somebocy know a recent tool to do it ?
thanks,

Java and Microsoft technology don't mix too well. You'll probably want to look into some technology that allows you to control (D)COM objects from Java. I've heard there's a project called Jacob that does that. Google it.

Similar Messages

  • 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

  • BexAnalyser : compatibilty of WB created in Excel 2010 with Excel 2003

    Hi all,
    I'm trying to define the compatibilty of worbook created with BexAnalyser (Excel)  2003 with BexAnalyser 2010.
    When a workbook is created in 2003 version and saved with 2010 version and opened with BexAnalyser 2003, I'm loosing the textelement (available by the Information bouton).
    For displaying this information, I have to turn into creation mode and displaying the information by quoting the radio bouton in properties panel.
    In an other case, when i'm creating a worbook with Bexanalyser 2010, i cannot open it with 2003.
    Do you know if Worbooks that are created in BexAnalyser 2010 have a chance to be compatible (by two ways) with BexAnalyser 2003.
    For information, we installed FEP 200 and FEP 201 and the SAPGUI is 720.
    Thank you in advance.
    Cedric

    As an update...
    I verified the Control ID in Outlook 2003 to be 5621.
    I have also downloaded a handy tool which is a bit more friendly for figuring out all the MS Office 2010 control ID's: http://www.add-in-express.com/downloads/mapi-store-events.php
    However, the tool confirms that the ID for OOF in Outlook 2010 is STILL 5621.
    Just for grins, I disabled the MailBox Cleanup utility on the same page by identifying it's control ID (7092), grey's out no problem. But I can't get the OOF button to go grey.

  • Excel 2003+ exports are actually being saved as .mhtml documents. How to export as true .xls?

    Hi All,
    I am new to OBIEE and was confused about why exporting report views to Excel renders them as .mhtml documents.
    I am using version 11.1.1.5.0
    What I have tried doing so far is this:
    Open Dashboard
    Click 'Export' link under my target Analysis within the Dashboard
    Excel 2003+
    Save As: "SampleFileName.xls" /// type: Microsoft Excel 97-2003 Worksheet
    Open the saved file
    Get the following warning:The fild you are trying to open, 'SampleFileName.xls', is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now?
    Click 'Yes'
    (the file opens)
    Click 'Save As'the default 'Save as type' shows "Single File Web Page (*.mht, *.mhtml)
    I was told to look into using the Delivery Manager APIs to see if I could export the Analysis as a clean Excel document. Is this the right place to look? If so, how would I go about implementing? Are there certain permissions I need within OBIEE in order to implement?
    If you have other suggestions, please let me know.
    Thanks!

    I managed to dramaticaly reduce the embedded code, by changing some export settings detailed below. It appears to be the fonts embedded as base64 by default. The following works well at reducing the size although not completely eliminating it.
    options.embedRasterImages = false;
              //options.compressed  = true;
              options.includeFileInfo = false;
              options.preserveEditability = false;
              //options.includeVariablesAndDatasets = true;
              //options.slices = true;
              options.fontType = SVGFontType.OUTLINEFONT;
        options.fontSubsetting = SVGFontSubsetting.None;
        options.optimizeForSVGViewer = true;

  • 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

  • Jakarta POI Excel97-2000 (Excel 2003?)

    Hi All
    I need to read data from Excel 2003 spreadsheet using my java program.
    I looked at Jakarta POI, and JDBC-ODBC bridge options.
    POI says Excel97-2000
    Creating system DSN does not show Excel 2003 options. It shows Excel97-2000, Excel 3.0 etc
    My environment is Windows XP 2002.
    Can I read Excel 2003 documents using POI?
    If I deploy this program on a machine which has earlier versions of excel on it will it be able to read.
    I just have plain text in excel spreadsheet.
    Please let me know.
    Thanks
    bib

    Hard to answer this question definitively because it very much depends upon exactly what is in the file. If you have saved a complex, formatted document that makes extensive use of features that were introduced into Excel for version 2003 then you will face problems. If the file contains simply plain text, then you should be fine. Most of the API authors base their product on an earlier version of the BIFF8 format to ensure compatibility with as wide a range of Excel versions as possible. That is why they all mention that the API will handle files that are based upon a specific version of Excel. Hopefully, you will be fine distributing the application onto machines that run earlier versions of Excel.
    By the way, have you also considered JExcel? It handles a few things differently to HSSF (POI) and you may prefer the way it approaches parsing an Excel spreadsheet file and exposing it's contents.

  • DAQmx VBA for Excel 2003

    Hi,
    I'm trying to control a NI6128 via VBA. I'm using Excel 2003 and tried several of the samples I found in the developer Zone, none of them seem to run. I think there is a fundamental error somewhere.
    But, the VB6 drivers  suppose to run under VBA and that is suppose to work under Excel 2003?
    Peter

    Check out some of these links about programming in VBA.  You might have to make some of your own code, I haven't been able to get those examples to run either.
    http://digital.ni.com/public.nsf/allkb/B22FE2B0F9C8935286256E920073DA07?OpenDocument
    http://digital.ni.com/public.nsf/allkb/735848148B5B4964862571F5004692C7?OpenDocument
    http://digital.ni.com/public.nsf/websearch/B22FE2B0F9C8935286256E920073DA07?OpenDocument
    I hope that this helps.
    Applications 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.

  • Printing Excel Instance from InfoView using Excel 2003

    Hi
    I have problem with printing Excel instance within InfoView. We are using Active X as viewer - but when user schedules report in Excel and when it opens that instance - it opens in Web Excel viewer within InfoView. At that point there is no standard menu if user uses Office 2003 or actually Excel 2003 on its own machine so user cannot print instance. Can anybody help with this. If you try to open instance on machine that has Office 2007 there are no problems since instance gets open in full Excel.
    Thanks

    What version of Crystal Reports are you using?  Any service packs or hot fixes installed?
    Can you open other xls files with 2007?  
    Have you ever exported to excel before?
    I export to -excel (97-2003) data only- and open the files with Excel 2007 with no problems. Excel 2007 complains about the old format (xls) and wants to convert it to the new excel format. I alsways ignor it.
    Maybe the 'garbage' you are seeing is because the layout of your crystal report is not working for the export. Is all the data there but you have extra cells and/or lines, or the data is pushed to the left? I find that I must have the fields packed tightly with no space between them and no space above or below the fields, or I get extra cells between and lines above or below them.
    Most of my exports are detail lines with a single line header and columns are set to match the detail line. When exporting multiple lines where the fields do not line up exactly with the ones above them, I may use one or more empty text fields that matches the size of the fields above them to fill the empty space. Sort of like:
    line 1:{field1.}{field2...}{field 3}
    line 2:(text...}{text.....}{field 4)
    And you may need to turn off 'can grow' on all fields as they may cause miss-alignment. All the data will be there when you export it, even what you can not see in Crystal. You will just need to format the cells in Excel to see it.
    Debi  (hi Don)

  • Report Generation Toolkit with Excel 2003 and Excel 2000

    Hello,
    I'm using the Report Generation Toolkit to generate an Excel report from an Excel template.
    The "NI_Excel.lvclass" is included in the "source" section of the application builder options.
    I create an exe file on  a PC where Excel 2003 is installed. On a Notebook, where only Excel 2000 is installed, the application crashes at the generation of the report:
    I guess the problem is the different version of Excel but I don't know. On the developer PC with Excel 2003 it works fine.
    In this document it's only talked about different Word versions.
    How can I use the Report Generation Toolkit here?
    I'm using it that way:
    Regards

    Oh, it seems that the Report Generation Toolkit "only" supports Excel XP/2003/2007.
    I think, that's the problem.

  • I can't transfer data properly to Excel 2003 with the report generation toolkit.

    I have a table with number to transfer into Excel. I use EasyGraph.vi and it works correctly with Excel 2000. But when I try the same program to transfer my data into Excel 2003, the data are not transfered correctly. When I have for example 0,56, it is read as text in Excel and when I have something like 53,300 Excel 2003 read this 53 300 as if there was no coma.
    Do you know what's happening with Excel 2003 ?

    Separators have always been a pain in Excel !
    A work around is to avoid using any separator at all, and to format numbers as power of 10.
    For instance :
    0.12345 -> 12345E-5
    12.345 -> 12345E-3
    The attached vi does the trick.
    Chilly Charly    (aka CC)
             E-List Master - Kudos glutton - Press the yellow button on the left...        
    Attachments:
    NoSeparatorEnumbers.vi ‏20 KB

  • 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

  • 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

  • Exporting SAP report to Excel 2003 - cannot use Excel icon

    Good morning folks
    We have recently installed Excel 2003 and since then we are unable to export reports from SAP (eg ad hoc query) directly into Excel by clicking on the Excel icon - a blank Excel screen is displayed. Any assistance please.
    We are still able to export to Excel by clicking on the Print Preview icon and then clicking on the Excel icon.
    many thanks
    Dawn

    My users misled me! They were not exporting directly to Excel at all but instead to Excel embedded in the SAP Gui! I have managed to get them to do this again by changing the security settings on Excel as follows: Tools > Macro > security settings - changed from Low to Medium and ticked both boxes in Trusted Publishers.

  • 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

Maybe you are looking for