Re: Forms Version Control?

In article <31E58DF9.67C2_at_neosoft.com>, Douglas Scott <dsscott_at_neosoft.com> says:
>
>We have an in house created program that stores information about a form
>such as who is currently working on it, status (beta or production),
>etc. This program runs on a VAX, but we're converting to Developer 2000
>on PCs and Macintoshes and don't know what to do about controlling the
>application versions.
>
>What is everyone doing about controlling application versions within
>Developer 2000 (especially in mixed platform environments)?
>
>Douglas Scott

We use a product called PVCS under a windows 95 environment. We have trialed many 'version control' products but none of then seem to offer a complete solution.
PVCS is good if you only want to 'check out' and 'check in' modules etc. It has promotion groups so you can see what modules haven't been tested etc. It is still a bit buggy (ie. it crashes if icons are pushed - windows 95). Instead you use the pull down menu.
We have forms 3.0 and forms 4.5 applications in PVCS. The forms 3.0 modules are developed on a UNIX box (SUN) while the 4.5 modules are developed under windows 95.
Basically all source is stored on a single file server (Novell in this case).

What we have found lacking is the ability to track various product versions to various customers.......

Mark Brady - Senior Computer Analyst
BHP Information Technology
Newcastle, NSW Australia
Telephone: 61 (49) 40-1638 Fax: 61 (49) 40-2165 e-mail: brady.mark.md_at_bhp.com.au Received on Fri Jul 12 1996 - 00:00:00 CEST