If you prefer to use a different scheme, such as 1.A, you can override the default mechanism with one of your own written in the JMDL programming language. How to do this will be covered in an upcoming edition of this column titled JMDL Programming. Role of History, Revisions and Transactions Think of history the history of any topic that interests you. There are aspects of history that offer inspiration and challenge you to greater heights. Other aspects offer you an opportunity to learn from the past and not make the same mistakes.
History also offers a foundation upon which to build bigger and better things.
Its ability to capture transaction history is one of the key differentiating values of ProjectBank when compared to any other engineering design environment I am familiar with. The concept of concurrent editing, discussed in the May 2000 edition of this column, is possible because ProjectBank captures transaction history. A transaction is the act of saving any changes to the ProjectBank data store. Typically, it will comprise of a design file revision. You use the ProjectBank Explorer dialog for either of these actions.