To use Workbench with sources on Unix or OpenVMS, you just need to set up access to your sources from your PC. You can do this with a mapped drive, or you can use Workbench's FTP toolset. Once you have access to your sources, you can edit your code with Workbench, and then use a terminal session to switch to your Unix or OpenVMS system for building and running.

(Note: You could also set up your code configuration for building on Windows, which would enable you to build and run your code from within Workbench. If you eventually plan to deploy your application on Windows, this could be one of your first steps.)

For example, one customer uses Workbench with their sources on a SCO Unix system. They use a mapped drive with a product called VisionFS. They check out sources in their Unix terminal emulator window (using PVCS), edit their code in their Workbench window, and then switch back to their Unix session to compile, link, and run.

(Note: If you are planning to use VisionFS, be sure to use the "-s3" Workbench option, which does a more complete job of saving files over this type of connection.)

An alternative to mapped drives, Workbench's built-in FTP capabilities enable you to import source code directly into the editor from any system on your network. You can set up one or more customizable FTP sessions to your sources. (For example, you can specify firewall and proxy specifications and set case sensitivity for filenames.) The interface provides the illusion that you are editing sources directly on the remote system. Read more about Workbench's FTP toolset. (.pdf)