Released on September 27, 2022

Bug Fix: “Update with new BOQ” function ignored forced selling prices in the minutes

Update with new BoQ (Converter Match both BoQs) - Merge also Minutes fields TakeForcedSellingPrice, ForcedSellingPricePerUnit

Bug Fix: "On_After_Create_PDF" wrongly taken into account

The recently implemented event On_After_Create_PDF cancelled the Export to PDF operation invoked from the report generator when no macro was associated to this event.

Bug Fix: Excel sessions controlled by QDV could attempt to close sessions of other users

When attempting to close Excel sessions started by QDV under TSE or CITRIX environments, QDV attempted to close all sessions for all users but of course if failed due to permissions. However, it took time to close Excel properly. This fix also solved a similar problem with the external Excel Gantt application : when QDV checked for existing Excel sessions, it checked for all users on the machine.

Bug Fix: Some PDF files were invalid

QDV report generator added some null characters at the end of PDF files when several pages have to be assembled together. This resulted in PDF files not usable by some systems.

Change: All files updated when published by ClickOnce

So far, not all files were updated at client side when a publication was carried out to the server. Now, when the client runs ClickOnce, any file modified at server side is replicated at client side, even if it’s not a QDV file. Some files were updated only when a new release of QDV was published.

This means that any change in E.g.: Custom_Articles.dll, Custom_Function.dll, Custom_Connection.dll or even a simple setting changed in the XML files through the ClickOnce publishing tool will be replicated on the client.

Also, because when you use ClickOnce, you want your client to be inline with the server, the client MUST accept the changes once they are downloaded. Before this change, he was prompted and could postpone the update.

The synchronization is not carried out at startup but after a little while (about 30 seconds) or when the user presses the update button.

Bug fix: Versions incorrectly tested

Because we recently published the 1000th beta release (which means 1000 beta version since the beginning of QDV 7 in 2008) the internal algorithm which compared the remote and local versions could fail to detect a new release. They are now based on x10000 instead of x1000.