Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved PB 2017 R3 SaveAs XLSX crash

  1. Issue
0
Votes
Undo
  1. Chris Baldone
    Chris Baldone
  2. PowerBuilder
  3. Thursday, 7 March 2019 18:54 PM UTC

I have an existing application that we have recently upgraded to PB 2017 R3 Build 1880. 

The code does:  dw.SaveAs ( ls_save_pathname, XLSX!, TRUE)

This code has been in place since our use of PB 8, we only had to change to XLSX at one point.  The version of Excel on the Windows 10 machine is 2016.

After the upgrade, the code works fine on my development machine in both the IDE and as a standalone install.  When I put it on a VM that mimics what the customer has, all of my code that saves to XLSX fails.  I can change that to TXT! and it works, but Excel is not working.  I have not seen anything about compatability issues with Excel.  I am not even sure the version is the problem at this point, but it is looking like a possibility.

Any ideas?

Making data window display only makes drop-down-li...
JSON->XML and XML->JSON
Responses (4)
Chris Baldone
Chris Baldone Accepted Answer Pending Moderation
  1. Thursday, 7 March 2019 18:56 PM UTC
  2. PowerBuilder
  3. # 1

Forgot.

The SaveAs causing the application to just sit there for about 10 seconds and then it closes out completely.  No messages or anything shows up, just gone.

Comment
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 7 March 2019 19:00 PM UTC
  2. PowerBuilder
  3. # 2

Have you tried saving to a different Excel type?

As I recall there are about a dozen different Excel "SaveAs" types. If Excel is on the platform then perhaps that version of Windows doesn'l like the TYPE you specified.

Also, is the Excel exe in the PATH variable? Could it be that the code cannot find the Excel app?

 

Olan

Comment
Chris Baldone
  1. Chris Baldone
  2. Thursday, 7 March 2019 19:05 PM UTC
I am checking those things now. A previous version of the same application, done in PB 12.6, works fine on the same machine that this one fails on. The only difference is the version of PowerBuilder
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 7 March 2019 19:36 PM UTC
  2. PowerBuilder
  3. # 3

Hi Chris;

   The XLSX feature in a deployed Appeon PB EXE is basically the same as PB 12.6.

Here is a deployment check list though for PB2017Rx:

1) Use the PB Packager utility to build an MSI that includes Excel 12 (XLSX) support ..

2) Make sure that the PB Excel files are deployed via #1 above or copied into the PB App's EXE folder, as follows:

    PBDWExcel12Interop170.dll,     Sybase.PowerBuilder.DataWindow.Excel12.dll

3) Make sure that the "Sybase.PowerBuilder.DataWindow.Excel12.dll" file is registered in the O/S's GAC

    The PB Packager's MSI should do that.

    If you copied the files, then you will have to run the GAC utility manually

4) The advanced Excel features need the .Net framework run-time to be installed (v3.5 or higher)

5) Note that there are 32bit and a 64Bit Excel files. Make sure that you deploy the correct bitness.

HTH

Regards ... Chris

 

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 7 March 2019 21:37 PM UTC
Hi Chris;

The "Packager" should have put that directly into the GAC if I recall correctly ...

Have a look in ... C:\Windows\Assembly - or -

At the DOS command prompt, run: gacutil -l | more

Regards ... Chris
  1. Helpful
Chris Baldone
  1. Chris Baldone
  2. Friday, 8 March 2019 17:07 PM UTC
The Excel12.dll missing was the issue, thx for all the help from everyone
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 1 December 2023 19:37 PM UTC
Hi Chris;

That is awesome news .. I am super glad that you found the issue! :-)

Regards ... Chris
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 7 March 2019 21:08 PM UTC
  2. PowerBuilder
  3. # 4

Use Excel8! instead. Those extra files and the .Net framework are only needed by XLSX!.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.