Released on April 8, 2022

Bug Fix: Deletion of collapsed branches in Gantt diagram led to error

In the “planner” tab of QDV, when using a WBS-type Gantt diagram. I was impossible to delete a collapsed group. That led to an error message.

Bug fix: QDVTools4XL Gantt – Issue at the first use

If the Tools have never been used, running the Gantt application at first time was giving an issue due to the global parameters. Fixed.

Bug Fix: #1725: cannot VACUUM from within a transaction

Depending on selected option (Add/Replace data) on Convert and selecting read only database in some cases there was a message that database is read only / not accessible, but in some cases the state was broken causing errors afterward. There is now check and message in case user selects read only Article or Set databases as target of conversion.

New: Qdv Long path support has been enabled (full paths exceed 260 characters)

According to Microsoft documentation, net 4.8 supports long paths by default, however it has been identified that Windows setting longPathAware is needed for proper long path support in QDV so it has been added to application manifest of QDV, QDV Converter and QDV Management tools to support paths longer than 260 characters.

Enable Long Paths in Windows 10, Version 1607, and Later. Starting in Windows 10, version 1607 - released on August 2, 2016, MAX_PATH limitations have been removed from common Win32 file and directory functions. However, you must opt-in to the new behavior.

To enable the new long path behavior, both of the following conditions must be met:

·The registry key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled (Type: REG_DWORD) must exist and be set to 1. The key's value will be cached by the system (per process) after the first call to an affected Win32 file or directory function (see below for the list of functions). The registry key will not be reloaded during the lifetime of the process. In order for all apps on the system to recognize the value of the key, a reboot might be required because some processes may have started before the key was set.

You can also copy this code to a .reg file which can set this for you, or use the PowerShell command from a terminal window with elevated privileges:

New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force

This registry key can also be controlled via Group Policy at Computer Configuration > Administrative Templates > System > Filesystem > Enable Win32 long paths.

·The application manifest must also include the longPathAware element.

<ws2:longPathAware>true</ws2:longPathAware>

</windowsSettings>

</application>

Bug fix: Reading ProMo+ project not belonging to (sub)branch of current user

When reading a ProMo+ project in an estimate, it was checked if the project belongs to user’s branch or sub branch, however the user could have been granted access also to projects in other branches, but this wasn’t checked so there was incorrect message: 'Current user does not have permission to read the project.' in such case.

Bug Fix: Deleting Quantity_Number field did not recalculate the lines immediately inside sets

Hitting “Delete” key in Quantity_Number column didn’t not immediately recalculate the lines. The problem also happened in Feed_Quantity_Number columns.