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

Resolved Save As Excel 5 or Excel 8

  1. How-to
0
Votes
Undo
  1. Yasir Masood
    Yasir Masood
  2. PowerBuilder
  3. Monday, 14 March 2022 18:04 PM UTC

Hi,

We have an issue with the Save As function in our application. When the user tries to save a reports as Excel 5 or Excel 8, it can take 4 or 5 minutes to save the report.

What could be causing this issue? We are using PB 2017 R3 Build 1858, SQL Sever 2019 (on Azure) and hosting using TS-Plus.

Any help would be appreciated.

Thanks

Yasir Masood

 

 

 

PowerBuilder 2017R3, 2019R3 and GIT repository
Calculation errors with LongLong datatype
Accepted Answer
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Monday, 14 March 2022 20:03 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi, Yasir -

Chris beat me to the punch with his question!

Based on the limited information you've given us, if I were to guess, I'd say it is network and/or anti-virus related.

In a test, using an app locally-running on my PC, built with PB 2017 R2, I was able to save a DW contain 63,416 rows of 29 columns (containing "real" data) in Excel5 format to my hard drive in 2.4 seconds. Saving same in Excel8 format took longer, 15.7 seconds.

Regards, John

Comment
There are no comments made yet.
Responses (4)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 14 March 2022 19:45 PM UTC
  2. PowerBuilder
  3. # 1

Hi Yasir ;

   How many DWO rows & columns are we talking about being saved to Excel?

Regards ... Chris

Comment
There are no comments made yet.
Yasir Masood
Yasir Masood Accepted Answer Pending Moderation
  1. Monday, 14 March 2022 21:09 PM UTC
  2. PowerBuilder
  3. # 2

There are 382 rows and around 70 columns on the DW

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 14 March 2022 21:15 PM UTC
Hi Yasir ... that is an insignificant # of rows to cause that performance problem, PB App wise. If you perform this SaveAs() on the developer machine (ie W10) and it works well - then I would look for the issue being Azure related. Just my $0.02.
  1. Helpful
Yasir Masood
  1. Yasir Masood
  2. Monday, 14 March 2022 22:23 PM UTC
Thank you guys.
  1. Helpful
There are no comments made yet.
Yasir Masood
Yasir Masood Accepted Answer Pending Moderation
  1. Monday, 14 March 2022 21:12 PM UTC
  2. PowerBuilder
  3. # 3

John, what other information would help you?

Comment
John Fauss
  1. John Fauss
  2. Tuesday, 15 March 2022 02:24 AM UTC
When trying to diagnose a problem like this, It's helpful to know the size (rows/columns) being saved and also what things you have tried in order to troubleshoot the issue. For example: Does it save OK as a .csv (comma-separated value) file, or Excel12 (xlsx) format? Is the file being saved to a file on a local hard disk, or on a network drive? Have you tried both? Any difference in performance? Is performance also poor when reading the Excel5 or Excel8 format file from the same location as where it was saved? When I ask a question on this or other forums, I try to place myself in the shoes of the person that would respond and include all of the information I imagine would be helpful. In this way, you help us help you.



Glad to see your issue is resolved! Best wishes, John
  1. Helpful
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.