Re: Forms Version Control?

In article <31E58DF9.67C2_at_neosoft.com>, Douglas Scott <dsscott_at_neosoft.com> wrote:
>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 have a central library for our source, and one individual is in charge of keeping the library up-to-date. Each programmer has read access to the library, and is expected to get a current copy of a form before beginning any maintenance. Upon completion of an update, the programmer submits the modified source to the librarian, who stores it into the library. It is a manual process, with a paper-trail used to keep everything synchronized--works just fine in a small group.

For run-time, each form has a built-in hard-coded version number, and checks its version against it's corresponding version specified in a database table. If these do not agree, the form issues a message and terminates. We hope this will prevent clients with out-of-date versions from running after an upgrade.

Regards,
Steve Cosner Received on Fri Jul 12 1996 - 00:00:00 CEST