JCOM example and Excel 2003

Following the instructions to get the jsp2com example running with Excel 2003 results in a JSP compilation error.
The generated classes contain an interface declaration for Application, i.e. Application.java contains
package excel;
public interface Application {
but the JSP tries to instantiate it, i.e. line 40 in the JSP reads
excel.Application app = new excel.Application();
Of course this doesn't work. Any ideas what has changed and how I can get this example to run?
Thanks in advance!

Hello,
First you can try checking if you have configured your apset to work with xltx.
1. Open BPC web admin and select AppSet Parameters
2. Check ALLOW_EXTENSIONS and DEFAULT_EXTENSIONS if you have xltx there
3. If not, add and click on update
If this continues to happen, check note  "1579344 - Office 2007 extensions not loading in BPC 7.5 SP6 for NW". This can be a program error, but note that it only happens for some templates.
Hope it helps
Debora

Similar Messages

  • GW8 and Excel 2003

    Can anybody else reproduce this...?
    GW8.0.0 ships with gwxl2007.xla 109 KB 06/12/2007
    when run on Windows XP with MS Office 2003 I am seeing runtime errors the
    first time I attempt a save back into GW DMS, I hit save a second time and
    all appears to go ok.
    If I remove gwxl2007.xla from C:\Novell\GroupWise (or C:\Novell\Program
    Files\Novell\GroupWise for fresh installs)
    and from C:\Docs and settings\profile name\Application
    Data\Microsoft\Excel\XLSTART
    and roll back to gwxl97.xla 127 KB 08/06/2008 from GW7sp3hp1 client,
    I no longer get this problem,
    and, provided that I Save then close via small X and then exit, the DMS
    integration is ok.
    thx
    Simon

    Simon,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • Excel 2007 and Excel 2003 format

    Hi all,
    we have some problems with Excel file format on BPC 7.5NW SP06:
    1- We save input schedules or reports woth Excel 2007 file format. Then when we try to open these report they are corrupted (we click on "Open" and nothing happens). We can download the report from UJFS. The xltx file is corrupted. We can change th file extension to xls. Then we can open the report again.
    2- Is it possible to define the default extension when we save input schedules and reports? By default xltx is selected. We want to have xlt selected by default.
    thanks for your help,
    Romuald

    Hello,
    First you can try checking if you have configured your apset to work with xltx.
    1. Open BPC web admin and select AppSet Parameters
    2. Check ALLOW_EXTENSIONS and DEFAULT_EXTENSIONS if you have xltx there
    3. If not, add and click on update
    If this continues to happen, check note  "1579344 - Office 2007 extensions not loading in BPC 7.5 SP6 for NW". This can be a program error, but note that it only happens for some templates.
    Hope it helps
    Debora

  • I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 profession​al. The create new report VI opens Excel but throws error (-21471672​62- from automation open VI) when I try to open MS word. please help...

    I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

    Hi Leo22,
    Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
    Jeremy L.
    National Instruments
    Jeremy L.
    National Instruments

  • Crystal 2008 and VBA in excel 2003

    We have currently crystal reports in VBA form in excel 2003 using Crystal XI Release 2. when I tried to migrate this report to "Crystal Report 2008 SP2" in VBA, I only found following reference 12.0 library
    Crystal Activex Report Viewer Library 12.0 (Crviewer.dll)
    but I couldn't find any reference library for (Craxdrt.dll) for crystal XI Release 2 it use to be
    "Crystal reports Activex Designer Run Time Library 11.5";
    so If i use 12.0 CRViewer.dll in VBA then I can create report object for it if "Craxdrt.dll"; is missing.
    thanks

    Hello,
    This is a [duplicate posting|crystal report 2008 and VBA in excel 2003;.Please do not cross post the same question to multiple forums. Here's a link to the [Rules of Engagement|http://wiki.sdn.sap.com/wiki/display/HOME/Rules%20of%20Engagement] for reference.
    Sincerely,
    Dan Kelleher

  • OBIEE 11.1.1.7 Exporting to Excel 2003 and 2007 difference

    Hi
    I have a simple analysis, a couple of measures, some formatted so tat if they are negative show them as Red, minus, 1 decimal and thousand separator. Another measure is not formatted to be Red, just black, minus, 1 decimal and thousand separator.
    So ... now to the issue. When I export to Excel 2003 the measures are fine, the numbers are numbers, all fine and dandy.
    When I export to Excel 2007+ ... the red minus numbers are now text and impossible to change them all to number. I can only convert to number those that are less than 1000 ... the rest are just impossible.
    The other measures, the ones that are black, minus, 1 decimal and thousand separator ... are numbers in Excel 2007+.
    Why?
    What can I do to solve this?
    Kind Regards

    Sorry guys ... forgott to say that I'm not the one exporting to Excel ... is my business user and I cannot ask them to save the reports to another format or to cast a column or more?
    I will try them both and see what happens ... but this is something that Oracle must fix. It's the year 2013 for godness sake!! This is not a Beta software. In my opinion this is so ridiculous I can hardly find words for it hahahaha
    I have tried to cast and convert ... well that doesn't work and I found that some people are using macros to convert text to numbers in Excel ...
    Sub txttonum()
      For Each tcell In Selection.Cells
      If TypeName(tcell.Value) = "String" Then
      tcell.Value = Val(tcell.Value)
      End If
      Next
    End Sub
    As goes for the CSV option ... I just cannot ask my business user to copy from a CSV file to the Excel file they want to work on, not even if they are advanced Excel users.
    Thanks for your suggestions, I really that the cast would work ...
    Any other suggestion.

  • BPC 7 : Excel 2003 and Excel 2007 Conflict

    Hi Experts,
                   I have created a template in BPC 7 MS on my computer which has Excel 2003 version.
    But when I try that template on another computer which has Excel 2007. The format (in the format Range) did'nt seem to work or it has diff effect on Excel 2007.
                   Is there really a conflict between them?? and cannot have different Microsoft Office version??  Or is there An Add-on that we have to Install so that Excel 2003 and Excel 2007 can be used at the same Time??
    Thanks,
    Bennie Jay

    Sorin:
    Situation
    I also have the same issue with Excel formatting in Excel 2007, and I found a work-around specifically to my issue.
    At the format section's CRITERIA, I have one entry: HEADING="New Budget" in the Column direction, apply certain color and number format to the cells of that column. However, I used Excel function CONCATENATE("HEADING=",EVDES("FINANCE",CATEGORY)) to come out with HEADING="New Budget", rather than just typing the string value.
    With the above exercise, in Excel 2003 the format would apply no problem, but in Excel 2007, the entire formatting went wild and broke. After I dropped CONCATENATE() and just typed in HEADING="New Budget", the formatting applied OK in 2007.
    Data
    We are currently on BPC 5.1 SP5
    The original report was built in Excel 2003
    Question
    Is there a setting in Excel that would allow me or bypass the restriction to use Excel functions to come out with CRITERIA definition?

  • I am trying to find an app that will interface with Windows XP home that will alllow me to download Excel 2003 files and run/change on an original Ipod. I have found Quick Office which is useless as cannot reduce font sizes to view a sensible area.

    Is there an app that will allow me to move and edit Excel 2003 spreadsheets to and from Windows XP home that is better than QuickOffice. QuickOffice does, but will allow the usual Apple zooming facility on my Ipod Touch ?
    Peter Campbell

    I have Office Plus on my iPhone.  I don't know if it's compatible with yours.

  • 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.

  • ? 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.

  • 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

  • VB6 and Excel loading then unloading immediately

    First off I posted this here
    http://social.msdn.microsoft.com/Forums/office/en-US/4c07879b-e033-4e8f-8266-95f9f606923a/vb6-and-excel-loading-then-unloading-immediately?forum=exceldev However I think this is the right forum for this.
    We have an old VB6 application that uses data from and to Excel 97-2003 XLS and
    Access MDB. This application is slated to be updated to VS2012 and VB.NET. In
    the mean time I have a glitch that I cannot seem to find the issue. When we
    load the VB6 app it opens Excel 2010 in the background for getting and setting
    data. We are set to roll out Office 2010 on everyone’s system and I am still
    unable to find why it works fine on two systems and not on others. With Office
    2007 everything seems to work just fine.
    What happens is when I look at the processes in Task Manager on my Windows 7
    Enterprise edition with Office Professional Plus 2010 system while loading
    the VB6 app I see?
    EXCEL.EXE *32 | "My user name" | 00 CPU | 10,132k | Microsoft Excel
    This is normal and stays in process the entire time I run it on my system. I also have
    this working on another end users system. However the issue and the fix I used
    on our two systems does not seem to work on other systems. I launch the VB6 app
    and it comes up.
    EXCEL.EXE *32 | "My user name" | 00 CPU | 10,132k | Microsoft Excel
    This loads in the processes and then immediately unloads without any errors. Then when I
    execute something that needs to use Excel I get.
    Run-Time error ‘91’:
    Object variable or With block variable not set.
    This only happens if Excel unloads immediately otherwise the program works great. There
    are no events in any of the event logs and our other IT guy said it is loading
    and unloading normally with out crashing.
    I have applied this to the systems http://support.microsoft.com/kb/926430/en-us . In
    all of my searching this looked like the best answer. However only two systems
    are working with Office Professional Plus 2010.
    Here are the references and components.
    References:
    Visual Basic For Applications
    Visual Basic runtime objects and procedures
    Visual Basic objects and procedures
    OLE Automation
    Microsoft DAO 3.6 Object Library
    Microsoft Excel 5.0 Object Library
    Components:
    Controls
    Desaware Animated Button Control
    Microsoft Common Dialog Control 6.0 (SP6)
    Microsoft Data Bound Grid Control 5.0 (SP6)
    Designers
    Dat Environment
    Data Report
    DHTML Page
    WebClass
    Code:
    Public xlApp As Excel.Application
    Public WBSetup As Excel.Workbook
    Public objWbCALC As Excel.Workbook
    Public objShtLEVELS As Excel.Worksheet
    Sub Main()
    ' There is more code here that is not specific to Excel issue
    Set xlApp = Excel.Application
    ' Get the workbook.
    Set objWbCALC = xlApp.Workbooks.Open("c:\temp\Calc.xls")
    Set WBSetup = xlApp.Workbooks.Open("c:\temp\Setup.xls")
    ' Get worksheet
    Set objShtLEVELS = objWbCALC.Worksheets("Levels")
    ' There is more code here that is not specific to Excel issue
    End Sub
    This is working on one system that had Office 2007 and was upgraded to Office 2010. Working on my system with Office 2010. The EXE file is ran from the server you can install it or add the OCX files to local system and register them with regsvr32. No
    new components have been added or changed to the actual VB6 application. It seems to work on two systems and not on other systems.
    However our test system have Office 2010 loaded on it and never had office 2007 on it. Maybe there is a residual left over file on it.
    Any ideas?
    www.ipdg3.com

    Hello,
    Thank you for your post.
    I am afraid that the issue is out of support range of VS General Question forum which mainly discusses
    WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
    and Visual Studio Editor.
    I would like to know whether you can get the same issue when you create/load a Visual Basic application rather than VB6 in VS2012. If the issue only occurs when you load VB6 app, as Andrew said, there are other better forums for
    VB6 app provided in this thread:
    http://social.msdn.microsoft.com/Forums/vstudio/en-US/6a0719fe-14af-47f7-9f51-a8ea2b9c8d6b/where-to-post-your-vb-6-questions?forum=vbgeneral
    For example:
    VB Forums
    VB City
    Best regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Printing problem Adobe Pro X from Excel 2003

    I produce a number of reports each month using Excel 2003 and printing/converting them to PDF documents.  All were nicely formatted and printed perfectly and reliably using Adobe 5.0 (ancient I know).  I recently upgraded to Adobe Pro X.  Now what once printed nicley only prints part of a page - about the right 1/3 is not showing.  Even when selecting "fit to 1 page wide and 1 page tall" in excel page setup doesn't fix the problem.  Changing the BINDING setting in Adobe doesn't fix the problem either.  Previously I selected Adobe Writer from my printer listing which I understand has been discontinued.  Now my only option is Adobe PDF.  Any suggestions?

    Interesting. My approach would
    1. Try on a different system if available. If still bad...
    2. Try to create a simple test application with CreateDC and StartDoc, and really nothing else not absolutely needed.
    Test that.  If it is good, look for other problems in your application (e.g. memory overwrite).
    If your little example is still bad, post it here and other people can try and compare your results.

  • I can't copy and paste formatted text within the same or between Word and Excel documents

    I run Microsoft Office Professional Plus 2010 (English) (Student Select)
    when I try to copy any formatted text or tables within the same or different Word documents I will always loose the formatting. This is also true if I try to copy formats or formatted tables within Excel or from Excel to Word, see example screenshot:
    When I have a look at my paste options via 'Alt', 'e', 's' or 'Paste special' it only lets me choose between "Unformatted Text" or "Unformatted Unicode Text", see screenshot:
    Here is what I tried already:
    - In the advance options menu all options are on "keep formatting"
    - I uninstalled and reinstalled the entire office suit but keep having the same problem!
    Any ideas?
    Thanks in advance,
    Boston

    I found the solution on another site, superuser.com, so I can't claim the solution as my own, but it worked for me. Kent Ng says: 
    I face the similar issue with Excel 2003. If you have installed Skype-Click-to-Call, just removed it to resolve this issue.

  • 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

Maybe you are looking for