Registered: 1158198299 Posts: 5,507
Reply with quote
Form segments are pretty neat little things. My most common use for them is for version information:
In my experience, version control of e·work procedures is often a lax affair. The ability to swiftly make changes promotes a less conscientious attitude than is normally required. Our experience of e·work development has included several mission critical and even life critical systems, and in these environments, proper version management is essential. I have a common library for every 'suite' of Procedures. In this Library I have a Form Segment with the name of the system as a whole, and the version number. This normally takes the format of 'x.y.z', eg 1.5.1. Each Procedure and Library file will have a similar common Form Segment with the build number. These are shown together on main forms in each Procedure. Every time a Procedure is updated, the Build number is incremented by the Developer. Every time a group of files is released to the customer, the main version number is also incremented by the project Manager. In this way, when you open a Folder, you can see the system version, and the build of the individual file. One extremely useful effect is being able to tell which version of a Library is actually being employed by the Procedure itself (it is not necessarily the last published, BTW (!). As we only deliver changed files to the customer, this enables to keep a very good track of exactly what has been published. As we manage several remote development contracts this is essential. This technique has allowed us to solve potentially difficult to diagnose problems when incorrect Library or Procedure files have been published and the system exhibits faults because of this. __________________ Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.