Highlighted
Absent Member.
Absent Member.
2554 views

[archive] Question on the EXCEL.def file

[Migrated content. Thread originally posted on 11 September 2007]

... When I compile this program, I keep getting errors on the EXCEL.def file.
...
I keep getting compile errors at the following line. Not sure why?
* _NewEnum
PROPERTY-GET, -4, @_NewEnum
RETURNING "IUnknown*", TYPE 13


There are so many things that can cause this, without seeing neither your program nor the .def file, it is almost impossible to state the cause.

One thought I have is that you refer to HP, do you use any compiler switches that are HP specific?

At any rate, can you try to compile this example and see if that works (no compiler switches):

       IDENTIFICATION DIVISION.
       PROGRAM-ID. ExcelHelloWorld.
      *====================
      *
      * Copyright (c) 1996-2001 by Acucorp, Inc.  Users of ACUCOBOL
      * may freely modify and redistribute this program.
      *
      * The purpose of this application is to show the absolute minimum
      * required to access a cell in a Microsoft Excel spreadsheet.
      *
       ENVIRONMENT DIVISION.
       CONFIGURATION                SECTION.
       SPECIAL-NAMES.
           COPY    "EXCEL.def".
                   .
       DATA        DIVISION.
       WORKING-STORAGE              SECTION.
       77  olExcel                  HANDLE OF APPLICATION.
       77  olWrkSh                  HANDLE OF WORKSHEET.
       77  olWrkBk                  HANDLE OF WORKBOOK.

       PROCEDURE DIVISION.
       Main.
           CREATE   Application      OF Excel
                        HANDLE           IN olExcel.
           MODIFY   olExcel          @Visible = 1.
           MODIFY   olExcel          Workbooks::Add()
                        GIVING           olWrkBk.
           INQUIRE  olWrkBk          Worksheets::Item(1) IN
                        olWrkSh.
           MODIFY   olWrkSh          Range("A1")::Value = "Hello world".

           ACCEPT   OMITTED.
           DESTROY olWrkSh.
           MODIFY   olWrkBk          @Close(BY NAME SaveChanges 0).
           DESTROY olWrkBk.
           MODIFY   olExcel          Quit().
           DESTROY olExcel.
           GOBACK.
0 Likes
7 Replies
Highlighted
Absent Member.
Absent Member.

RE: [archive] Question on the EXCEL.def file

This is my first Acucorp GUI program that will open, write, and then close an EXCEL file.

My GUI program, using acuthin, will prompt the user for a date range, read the information from a Acucorp vision file on the Unix server and then create and EXCEL file on the users PC that is running under Windows XP.

My Acucorp COBOL source code will reside and be compiled on the Unix server.

I have started out with a simple program that and I will build on this program. My program is very similar to the excel-ole.cbl.

When I compile this program, I keep getting errors on the EXCEL.def file. The EXCEl.def file was created using the Axdefgen utility. This EXCEL.def file was then moved to the copy library on the unix system.

../../COPYLIBS/EXCEL.def, line 283: RETURNING expected, NEWENUM found
../../COPYLIBS/EXCEL.def, line 283: PROCEDURE expected, RETURNING found
../../COPYLIBS/EXCEL.def, line 283: DIVISION expected, RETURNING found
../../COPYLIBS/EXCEL.def, line 283: identifier expected, RETURNING found
../../COPYLIBS/EXCEL.def, line 283: Missing PARA/SECTION
../../COPYLIBS/EXCEL.def, line 283: Can't recover, good bye!

I keep getting compile errors at the following line. Not sure why?
* _NewEnum
PROPERTY-GET, -4, @_NewEnum
RETURNING "IUnknown*", TYPE 13
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] Question on the EXCEL.def file

Is Excel.def in the COBOL program under special-names?

Does the porogram compile on Windows?
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] Question on the EXCEL.def file

Yes, the EXCEL.def is under SPECIAL-NAMES.

I moved the source program from the unix server to inside Acubench and compiled the program. There were no compile errors.

Do I need to keep the source program in Acubench?

I would prefer to keep all my COBOL source code on the unix server. We have a lot of HP MPE calls (SpeedWare AMXW) in our source programs. We were on a server running MPE before converting to unix. Most of our flat screens were converted from VPLUS on the MPE system to EdWin on the unix system. Our Acucorp compiler on the unix server has been altered to recognize the AMXW calls.

I am just now starting to convert the EdWin flat screens to GUI screens called through Acuthin.

Any thoughts or suggestions?
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] Question on the EXCEL.def file

I'm not an HP3000 expert but I though that HP 3000 referenced copybooks differently (archived in a COPYLIB). When compiling a simple COBOL program (developed in AcuBench or just on Windows) using copybooks are you able to compile on Unix? If not it seems to be that the Unix environment is not correct. Is COPYPATH being used or the compile -Sp option so that copybooks can be found?

You may want to contact Technical Support.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] Question on the EXCEL.def file

This is the compile statement on the unix server.

ccbl -w -x -o @.acu -Lo @.lst -Lf -e @.err -Sp ../../COPYLIBS -Cp -Ca -Di
-Dci -Dz -Ga -Zd $1.cbl
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] Question on the EXCEL.def file

Try compiling without any compile switch, if it makes a difference, start adding switches until you see what causes the error.

Btw, -Ga and -Zd does the same thing. -Zd is reduntant, you can remove that.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: [archive] Question on the EXCEL.def file

It was the -Cp switch causing the problem. After removing this swith, it compiled clean.

Thanks.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.