1. Richard Shakour
  2. PowerBuilder
  3. Tuesday, 30 January 2018 20:17 PM UTC

I have noticed this now for many years and now the same thing is happening in PB17.

After programming, running and doing things in PB17 for a bit, all of a sudden the script editors FIND command stops working.

Need to close down PB and restart and it works again.  Does his in all editors script, db etc.

Has anyone else run into this so I can validate a Bug report.

Ricardo Colarina Accepted Answer Pending Moderation
  1. Tuesday, 30 January 2018 20:32 PM UTC
  2. PowerBuilder
  3. # 1

Yes, happened to me a few times over the last 2 decades.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 30 January 2018 20:45 PM UTC
  2. PowerBuilder
  3. # 2

Hi Richard;

  FWIW: This has never happened to me since using PB for decades. All good in PB 2017 R2 as well, but I am using MR01 & R2 versions of PB on machines with 12 & 16G base memory.

Regards ... Chris

Comment
There are no comments made yet.
Miguel Leeuwee Accepted Answer Pending Moderation
  1. Wednesday, 31 January 2018 08:45 AM UTC
  2. PowerBuilder
  3. # 3

Yes, it happens to me all the time. Working on windows 10.

Mostly when working from home via RDP and PB was already open on remote pc when connecting.

 

Comment
  1. Miguel Leeuwee
  2. Wednesday, 31 January 2018 08:46 AM UTC
That is, when using the short-cut key ctrl+F to do the search.

  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 31 January 2018 16:35 PM UTC
  2. PowerBuilder
  3. # 4

Hi Miguel,

 

I have been using PowerBuilder for years too and have not had this happened to me. Please see if you have the latest build (1681) and do let us know if this still happens and under what circumstances. You may open a ticket if you feel this is a bug.

 

Regards,

Comment
There are no comments made yet.
Bruce Armstrong Accepted Answer Pending Moderation
  1. Saturday, 3 February 2018 21:44 PM UTC
  2. PowerBuilder
  3. # 5

I've run into it with PowerBuilder 2017 and reported it as a bug:  https://www.appeon.com/standardsupport/track/view?id=670

It's unfortunately titled because I thought it had something to do with my switching back and forth between single and dual monitors.

It's very hard to reproduce, and when I do experience it it's because I've spend a great deal of time editing in source code mode.  That's likely why I haven't seen it before, as I really haven't spent as much time in that mode as I have recently.

 

 

 

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.