Powerbuilder resources [closed]

Question

I'm recently working in a company where we use PowerBuilder extensively. The only documentation or resources we have access to is some basic course saying things like "Do A, then B and you'll get C". I was wondering if there is some better crash courses or tutorials for this language on the net or somewhere else which actually explain something instead of simply taking me by the hand.

Answer 1

"Better" sounds intimidating, since it's hard to tell how your learning style works and what's better for you. (I guess I like the ABC approach.) So, instead of listing things that will be hit or miss, I'll try one resource that has both quantity and quality. The PowerBuilder Developer's Journal has a large online archive of old and fairly recent articles online. (The current issue gets online pretty quickly, but I wouldn't venture to guess how quickly.) Like any technical journal, the quality of the articles can vary, but IMHO stays pretty high on average. They'll range in topic from navel-gazing speculations to detailed instructions on how to accomplish very specific goals. I'm not sure it's necessarily great for starting off, but it's a good place to go once you've dragged your way through the ABC tutorial in the PowerBuilder manuals.

Good luck,

Terry.

Answer 2

Unfortunately there is not much out there for PB, compared to other languages. Here are some useful resources on the web:

• Back when I was writing PB I found Google Groups was a great resource for finding information about specific issues with PowerBuilder code.

• Terry Voth runs a website called Sequel's Sandbox that has a lot of useful PowerBuilder resources. He's also on StackOverflow, so perhaps he can chime in with more info :)

One thing that we did was have any new PB developers run through the tutorial that comes with PB (Disclaimer: we had an enterprise version, I am not sure if all versions of PB come with the same tutorial). Anyway, this was a great way of getting started and learning your way around the IDE.