1. Jason Schultz
  2. PowerBuilder
  3. Friday, 10 November 2017 19:58 PM UTC

At our worksite, we're in the process of transitioning over to new developer machines (Win7 to Win10).  During this process, we've encountered some odd behavior within our PB 12.6 Classic (build 4098) on the new machines. If I open an object within PowerBuilder, I will not see all the expected contents of the object.  For example, maybe a new instance variable defined for a window control and maybe changes to various window functions/events. Outside of the PowerBuilder IDE, if I navigate to the same object being referenced (lets say a specific window.srw file), open it with NotePad, I will see all the expected 'raw' contents. I just don't see it within the PowerBuilder IDE.

If I go back to PowerBuilder UI and delete the object from it's specific .pbl and then import it (referencing the same object file), I will then see all the expected contents within PB IDE from that point forward.

Could there be some kind of 'disconnect' between all the individual PowerBuilder elements (pbw / pbt / pbl / pbg / etc) causing this issue?  What does PowerBuilder do internally when an object is imported?  Is there a way of performing these actions in 'bulk mode' against all the objects in our workspace vs. having to do a delete/import manually?  I've already tried Optimizing all the .pbl's and doing a full rebuild on the workspace but that didn't work. 

I appreciate any input / advice anyone can provide.    

Thanks,
Jason Schultz

Ronnie Po Accepted Answer Pending Moderation
  1. Friday, 10 November 2017 21:16 PM UTC
  2. PowerBuilder
  3. # 1

Hi Jason,

It seems that the PB IDE does not recognize (via the SCC interface) that the objects have changed.

Try adding the following to the Library section of the pb.ini file:

[Library]
SccDiffStrategy=08

Then restart PowerBuilder, perform a "Refresh Status" on the application target, followed by a "Get Latest Version..."

Let us know if that makes a difference...

Comment
  1. Jason Schultz
  2. Friday, 10 November 2017 22:16 PM UTC
HI Ronnie, thanks for the reply.  One thing I neglected to mention when I was describing our issue is that I did a 'get latest' within my PVCS exclusively and placed all source code in a separate folder on my new machine (my new starting point for development).  I do not use any source control within my PowerBuilder environment nor do I have any source control defined within my Application workspace.  I don't connect to source control within the PB IDE.  Sorry for not mentioning that in my original question.  I'm not sure if that impacts the situation, but wanted to clarify to see if any other options. Thanks.

  1. Helpful
  1. Ronnie Po
  2. Monday, 13 November 2017 17:37 PM UTC
Hi Jason,



It does matter that you are doing the "get latest" outside of the PowerBuilder IDE. If you are managing source at the object level (vs. the PBL level), then you must perform all SCC operations from within the PB IDE. I'm just guessing that on your Win 7 machines, you were also managing your PBL files with PVCS. Normally, you would not check in PBL files to source control. The PB IDE, in conjunction with an MSSCCI-compliant plug-in or client, would handle the importing and exporting of the contents of each PBL to the SCC provider.



Here's one quick check you can do: When you encounter a situation in which objects are missing on the Win 10 machines, copy those exact same PBLs back to a Win 7 computer, without manually importing anything into them. Are the objects still missing in the Win 7 environment?

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 10 November 2017 21:08 PM UTC
  2. PowerBuilder
  3. # 2

Hi Jason;

      Since PB 12.6 was never certified for W10, that might be your issue. However, I have v12.6 running OK on my W10 PC`s but,  I do not use PVCS. I know that PVCS does have issues with the PB Classic IDE`s under various circumstances. Most of the time is a conflict in resources with the JVM. The easy remedy there is to set the following in the PB.INI file ...

    [JavaVM]
    CreateJavaVM=0

This prevents the PowerBuilder IDE from instantiating a Java VM when it connects to a source control system. Hopefully, that might be your issue.

    The other suggestion would be to download the trial version of PB 2017 and see if the same weird behaviour is present in viewing your PBL object`s in the various painters on W10. PB 2017 is W10 certifies. One other thing to try as well with your PB 12.6 version is to make sure that you optimize all your PBL's in your Application & then perform a full build. The way the PB IDE manages PBL's (especially deletes & replacements) can lead to "ghost" objects being present. If the IDE picks up  "ghost" source at painter open time - weird behaviour like you described has been known to happen.

HTH

Regards .. Chris

Comment
  1. Jason Schultz
  2. Friday, 10 November 2017 22:18 PM UTC
Chris,



Thanks for the reply.  One thing I neglected to mention when I was describing our issue is that I did a 'get latest' within my PVCS exclusively and placed all source code in a separate folder on my new machine (my new starting point for development).  I do not use any source control within my PowerBuilder environment nor do I have any source control defined within my Application workspace.  I don't connect to source control within the PB IDE.  Sorry for not mentioning that in my original question.  I'm not sure if that impacts the situation, but wanted to clarify to see if any other options. I do plan on doing an optimize / rebuild to see if that resolves any issues.  I'll let you know.  Thanks.

  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.