OI 10 marked the introduction of a new licensing method, replacing the old `oengine.dll` stamping. Historically, the licensing information was baked into `oengine.dll`. If you wanted to “change” the characteristics of your OI system you could just drop in a different `oengine.dll` and, effectively, you had a new system. OI 10 introduces a separate licence metadata file called `revengine.lic`. It’s a simple XML file that looks like this (with some minor obfuscation): <OI> <Signature>PEe80-Uf189-5mg27-m1t80-00m4Q-9hih7</Signature> <SerialNumber>W10280784</SerialNumber> <NumUsers>10</NumUsers> <ExpirationDate>2025-05-21</ExpirationDate> <ExpirationType>0</ExpirationType> </OI> The `Signature` element is the important part. It’s a cryptographic signature over the real licence attributes – serial number, user count, expiry date and type – generated wit...
An old client recently got in contact about the system we had written for them in AREV in the early 90s and subsequently ported to AREV32. Over the years, we had added some bells and whistles including an incredibly specifically tailored OI export utility which we installed about 10 years ago. Just recently, we added another OI export utility, and it was working as expected. But now, the client has reported that when including a specific set of columns, the report just hung - no messages, nothing. Eventually they just had to kill it in the task manager. They wondered if this was in any way connected to the recent upgrade? Now here's where it gets interesting. The columns in question are used frequently throughout the system, displayed on entry screens, reports and the like with no issues, so we thought the client's concern might be justified. We spun up our test system and attempted to produce the report the client was trying to create. Immediately upon selecting the columns in...
Some seven years ago, REVDEX documented the then newly introduced concept of #region to allow folding of code. We find this to be incredibly useful when working on large commuter programs as it allows easy navigation between code sections. There's no point in reproducing the linked article, so briefly, you can bracket sections of code between #region regionname and #endregion regionname and then fold that section of code. Here's an example of one of our commuter routines with the various code sections "regioned". I'm able to see at a glance what a large program does. If I want to look at the supportingRoutines I can just dropdown the "Find label..." combo and select that option The editor then takes me to the line number where that region begins. However, there is a minor caveat to be aware of when we're cutting and pasting collapsed regions. In the following pseudo-code (with a nod to Jackson Structured Programming throwback for those as ancie...