I'm running the latest version of PowerBuilder 2017 R3 Build 1880 Cloud Edition.
I'm running into an issue where you remove a function call dependency that another object relied on. So of course, doing an incremental build reveals this problem. Can't open it directly in visual mode, not a problem, I'm used to editing the source. Op, wait, the object is not checked out. I go to check out object... PowerBuilder bombs EVERY TIME. I try to check out object directly on back end of source control, I edit the source, and at one point, after I reload PowerBuilder, it shows the object as checked out. I try to regenerate... bomb. I come back in, and the object has now disappeared from my list. After checking in and out, and trying to import the object into my library, I can no longer see the object, and the import process doesn't do anything at all. No notices about what happened to the object, whether it was imported or anything. At least older versions of PowerBuilder still allowed you to check the object out, even if it wouldn't compile, and simply let you know that. Now, you can't even do that, it blows the object away out of your object list, so where is it, and how do I get it back? Importing the object doesn't work period. Also, why isn't the check out feature working, and importing the object from source control like it should, without having to worry about whether it compiles or not. Shouldn't matter, I've done this a billion times in past versions without a problem. Why now? Help! Thank you in advance!!!! If I can't check out objects that don't compile without PowerBuilder blowing up all the time, not sure how this is supposed to work?! Is this problem duplicatable? Thank you!!!!
--Brian