In my first OrcaScript article "Using OrcaScript to Automate Your Build Process With or Without Source Control" (PBDJ, Vol. 14, issue 6), I focused on automating the build process using OrcaScript. The entire article was based on the assumption that we might be using a separate build machine. Because of this, I avoided using or connecting to the workspace to get the source control connection parameters or to look at the source control status of each object. This time, I'll make things a little bit easier by using the workspace and focusing on writing short scripts and a reusable script that prompts for a target name.

A Quick Reminder
The OrcaScript files that we will write here are just script files and need to be passed into the OrcaScript engine from the command prompt. In PowerBuilder 10.5 the syntax would be "c:> Orscr105 xxxxxxxx.orca". If you are using a different version of PowerBuilder, just use the correct Orscrxxx.exe file when you call your OrcaScript file. Also the batch files that I demonstrate with here are created for the Windows XP (sp2) platform and may need to be adjusted for different operating systems.