1. Jim Nesbitt
  2. PowerBuilder
  3. Wednesday, 12 April 2023 19:14 PM UTC

Hi 

Our standard practice is to use views in datawindows for retrieval.  This avoids putting complex SQL in datawindows. It also allows to change the view behind the scenes if we decide to use different tables in the view. 

We have to specify the update properties in the DW painter because of using a view, but benefits of views vastly outweigh having more complex SQL in the datawindow. 

If the select statement is changed to add in another column, the update properties then get trashed and have to be re-entered. I'm not sure why this is the default, as adding in an extra column shouldn't impact this. If SP update is being used, it's even more hassle.

If the default was to leave the update properties as is, this would be far better as it would probably be OK in around 99% of cases, compared to trashing them, where they need to be re-instated in 100% of cases. 

PB has operated like this for years, so we're used to it, but I've found Appeon very responsive, so thought it might be worth raising it.

Cheers

Jim

 

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 April 2023 19:25 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Jim;

  You are correct - unfortunately, that has been the DW Painter's behaviour since way back even into the PowerSoft days of PB.  :-(

   Please open a support ticket as an enhancement request to have this issue corrected.

Many thanks!

Regards ... Chris

Comment
  1. Jim Nesbitt
  2. Wednesday, 12 April 2023 19:43 PM UTC
Hi Chris - it's been around so long, you just get used to living with it. I think I started using 3.5 originally, but it's so long ago, I can't be certain. - You should have raised it years ago!



I'll mark this Q&A as solved



Cheers



Jim
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 12 April 2023 20:29 PM UTC
Hi Jim;

Yes, SP's are "in the same boat" on this aspect as well. Unfortunately, a PowerSoft / Sybase "legacy" bug. :-(

Regards .. Chris
  1. Helpful
There are no comments made yet.
Jim Nesbitt Accepted Answer Pending Moderation
  1. Wednesday, 12 April 2023 20:15 PM UTC
  2. PowerBuilder
  3. # 1

Hi Mike

I never knew it was requested from Sybase lots of times- you'd think it would be a quick win fix. We didn't have any support contract so just got used to living with it - we used SQLPreview for this before SP update was available so we never used SP Update much, I only thought about it because I had to change the SQLPreview to use SP Update for PowerServer and putting back SP update details is painful. 

I originally raised a Q&A about changing SP Update in code to avoid the trashing problem which resulted in this Q&A, Modify Datawindow to use Stored procedure for update using code . 

I've raised a support ticket with same name as this Q&A. Bug# 10065

Cheers

Jim

 

 

 

 

 

 

 

 

Comment
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Wednesday, 12 April 2023 19:40 PM UTC
  2. PowerBuilder
  3. # 2

If i wanted to annoy every developer, this is how i would have designed it.   

 

This was one of the most requested fixes for many years.  I think everyone got used to being ignored by sybase and just gave up asking for a fix.   

 

 

 

 

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.