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
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.