Package VRC

A Package VRC is a package, which is indicated by a VRC. Within each PVRC, various components can be created and/or modified. The advantages of using PVRCs are:

  • standard software cannot be overwritten
  • new software components can be developed and tested in a protected environment before releasing them to production
  • a PVRC does not contain all software components, only new or changed components
  • development authorizations can be set by PVRC

The software components that can be created and/or modified within PVRCs are:

  • Labels
  • Forms
  • Menus
  • Reports
  • Sessions
  • Functions (Include Files)
  • Program Scripts
  • Messages
  • Questions
  • Domains
  • Table Definitions
  • Dynamic Link Libraries
  • Charts

Package Combination
A Package Combination is a combination of individual PVRCs, but only one VRC from each package.
A working environment is determined by:
  • package combination code
  • various PVRCs
  • company number(s)
  • users
Assigning a Package combination to a user in a company:
This slide depicts two environments: a Production environment (OPER) and a Design Environment (DSGN). The Design Environment is based on the Production Environment because of the derived from structure of the Package VRCs. Everything that is created in the Design Environment will not affect the production environment unless it is released. 

Users are linked to a Package Combination in order to find the software components at runtime. 
Developers will create/modify software components. To be able to run the software components, the developer is linked to a package combination like the user. But in order to create new software components, the developer needs a Current Package VRC.  If authorized, the developer can switch between Package VRCs.

Related Posts:

People who read this post also read :


VRC present some problems faced with comparators future i think this is perfectly change
Thank you

Post a Comment


Twitter Delicious Facebook Digg Stumbleupon Favorites More