send large queries to the processing queues causing system-wide issues. In 1993 Cortex started supported vesting to Digital's new 64-bit Alpha line. In 1994, International Software Group Co. Ltd. (ISG) purchased Cortex. The beginning of the end for CorVision As early as 1987, Cortex recognized the growth in the popularity of the IBM PC, supporting wikt:diagrammatic editing of menus and data relationships in CorVision. In 1993 a client-server version was released, but not widely adopted. In 1997 ISG's work on CorVision-10 which was to herald the rebirth of CorVision onto the IBM PC platform stopped. CorVision-10 was proving very difficult to port and ISG finally refused to spend any more money on the now-dated system. 1994 saw the last innovative CorVision release: V5.11. The extra-fee Y2K release, V5.12.2, marked the end of development. CorVision as a legacy system CorVision still exists in a handful of companies that have not yet found the time or money to upgrade their existing mainframe systems. As CorVision runs on the VMS environment it is very stable but the search for CorVision developers and contractors to support these ageing systems is a problem. Since around 1999, companies have started appearing offering conversion tools to convert BUILDER code to compiled Visual Basic and Java. In 2005 CorVision guru Michael Lowery, now president of Order Processing Technologies, attempted to revive the CorVision franchise with CV2VB, a process to convert CorVision applications into .NET applications using a SQL server. CV2VB is OPT's third generation CorVision conversion and replacement modeler/code generator. It is in commercial service at former CorVision clients. Information is available at the CV2VB website. Application development A brief explanation of application development using CorVison. Application parameters The first step in developing an application with CorVision is to fill in the parameters which control the miscellaneous aspects concerning application-wide functions. The parameters fall into five groupings as follows: Heading, Title and Menu Information for the application. Development parameters which affect the CorVision working environment. Run-time parameters which affect run-time execution of the application (including Batch & Print Queue control). Application-wide navigation options. Application-wide standard menu items. Usually the default values for these parameters are satisfactory. CorVision however allows for these setting to be changed at any time during development. The parameters file (WP) is accessed at runtime so the latest setting are always used. Status Screen CorVision keeps the information behind the Status Screen up-to-date so that