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

Resolved SAVEAS XLSX! file is unreadable by Excel

  1. How-to
0
Votes
Undo
  1. Gordon Weil
    Gordon Weil
  2. PowerBuilder
  3. Monday, 23 August 2021 20:46 PM UTC

I have an application that creates a number of reports and saves them as Excel files with the XLSX! save as type and file extension.xlsx. All the reports open in Excel 2016 except one. The one exception can be saved with the EXCEL! SaveAs type and it opens fine but our security settings do not allow me to edit the file and my users will not stand for it anyway.

I have managed to successfully open the file if I do not write any data to the datawindow. I do not see any datawindow properties that relate to this but I may have missed something. I did try the XLSB! save as type but that gave the same problem ans XLSX!

Any suggestions for what I need to change with the datawindow or the way I save it to allow it to save and open?

  1. Excel
Cannot open library files (PBL) with PB 7 on PB 20...
Modify version Window appears after an SVN Update
Responses (3)
Gordon Weil
Gordon Weil Accepted Answer Pending Moderation
  1. Tuesday, 24 August 2021 14:52 PM UTC
  2. PowerBuilder
  3. # 1

The presentation style is Tabular. Other datawindows are Tabular and there is nothing I can see that is different about this datawindow.

Good question about the version. We use PB2017 R3 and your question reminds me I need to start testing with PB2021. Moving to PB2019 is not an option, we ran into a bug that never got resolved (and yes I should have pursued it with Appeon more but I just got burned out on that after the datawindow computed column sorting bug end rant back to the present).

I will try moving to PB2020 but it's been 2 years in a row we had to roll back from a PB upgrade in order to release on time so we will need to do weeks of testing before we feel comfortable committing to PB2021. I was hoping to resolve this sooner than that.

I can get this report to work by saving it as an XML report that my users can open in Excel. That may be my short term solution until I can verify that PB2021 works for us. Then if the problem persists I can get help with this using current version solutions rather than spending time on a version of PowerBuilder that I am hoping to move on from in the near future.

 

Comment
John Fauss
  1. John Fauss
  2. Tuesday, 24 August 2021 15:13 PM UTC
OK. Please let the Community know if there is anything else we can try to help you with. Good luck!
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 24 August 2021 01:39 AM UTC
  2. PowerBuilder
  3. # 2

Hi, Gordon -

What presentation style (Grid, Tabular, CrossTab, etc.) is the DataWindfow that will not SaveAs XLSX?

Is it the only one using this style?

Is there anything unique regarding this DataWindow?

What version and release of PowerBuilder are you using?

Comment
There are no comments made yet.
Chris Pollach
Chris Pollach Accepted Answer Pending Moderation
  1. Monday, 23 August 2021 21:12 PM UTC
  2. PowerBuilder
  3. # 3

Hi Gordon;

  FYI: The XLSX option uses the .NET Framework. I would check and see if a newer .Net version might cure this problem. I am using .Net 4.8 target pack on my current W10 machines with PB2019R3 and PB2021.

HTH

Regards ... Chris

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.