Released on May 26, 2024

Bug fix: Formulas with global variables were not updated after ComputeAll in Minutes in some cases

The problem occurred if a minute field had a formula which contained a global variable which was defined in the overhead. And in turn, that variable in the overhead depended on data from minutes or WBS. And if that WBS data changed, for example WBS_Quantity, the update was not reflected in the final minute field. The user needed to perform check and repaint.

Bug fix: Some overhead sheets were not correctly downgraded from 7.24 to lower versions

The "Planner data", "Cash data", "Material time frame" and "Workforce time frame" overhead sheets were not correctly downgraded from QDV 7.24 format to lower versions. If such migrated estimate was opened in an earlier version of QDV, for example 7.23, there were errors after Compute all and the affected overhead sheets didn't work properly.

Bug fix: Couldn’t open an older estimate that was updated to QDV 7.24 in very special cases

The problem occurred if there was an overhead workbook control, such as drop-box, which had invalid Input range, for example “1,2” in the control options. The estimate could be open and worked fine if the OS regional setting were set to EN. But in FR (or any culture where the decimal separator is a comma), the estimate couldn’t be opened and an "Invalid formula" error was displayed. Now such wrong data are detected during the upgrade.

Bug Fix: Macros lost in DOCM

A problem in a 3rd part component lead to lost of macros when a DOCM was used as a Word template.

Bug fix: Empty sheet Cash data(2) added in overhead workbook at Gantt activation

When a Gantt feature was activated in an estimate, and empty sheet named “Cash data(2)” was added in the overhead workbook. User had to refresh the overhead to display the sheet with data. Now the sheet has the correct name “Cash data” and is no longer empty.

New: Custom_Connection.dll extended

The Custom_Connection.dll has been extended and contains now a new method to change the Login passed to the license server. By default, the license server receives the Windows login (user name) but if needed in your environment you can use a specific Custom_Connection.dll (See SDK folder under installation folder). A new method has been added: GetLoginForLicenseServer() which returns a string. By default this function returns Null meaning that Windows login (user name) is used as before. Note that this new function is invoked only it the version of the DLL is greater than 4. So existing DLLs work as before.