What changed, between which versions

A month-end close that runs in the background can now be stopped from the screen, without asking support. It stops within seconds, after the stock or location it is working on. Everything already finished is kept, and a month stopped part-way keeps its previous closing values. The step list shows where the close stopped, and opening the screen again offers to resume it from there. Starting, stopping and resuming a close need the PROCESS right.

On some servers the SQL Server Agent job that runs the close in the background was owned by the Windows login that applied the 2026.2 upgrade. When SQL Server could no longer find that login, for example after the PC was renamed or the user was removed, the job failed before it started and the screen kept waiting without any message. The hotfix gives the job the same owner as the other DynaMod background jobs (sa). If a close still has not started after about 30 seconds, the screen now says so, shows the reason, and offers to run the close in the screen instead. If you choose to keep waiting, it tries the job again about once a minute, so the close starts by itself once the job is fixed.

Regenerate Stock Cost and Closing Stock Value for Locations showed “0 / 1 done” until each step finished, which on a large database can take hours, and Total Records jumped between thousands and 1. The screen now shows how many stocks have been recalculated out of how many, with an estimate of the time left, and how many locations are done, and Total Records always counts stocks, locations or periods. The log also reports progress every few minutes. Re-opening the screen during a close now shows the month being closed, and the Month-End close COMPLETED message stays on screen when it finishes.

When the close ran in the screen, it always recalculated every stock. It now recalculates only the stocks that changed since their cost was last worked out, as intended, for companies that use deferred stock costing. The figures are the same either way.

Starting, stopping and resuming a close now need PROCESS. Users with ACCESS only can open the screen and follow a close that is running.

A back-dated change moves the stock balance of every month after it, but a re-close in the background replaced only the chosen month, and a re-close in the screen went back over every earlier month instead of the later ones. Both now close the chosen month and every later closed month again, oldest first, and the step list shows beforehand how many months and locations that covers.

It could finish as COMPLETED, and mark the month as closed, without redoing the month it was working on when it was interrupted, so that month’s closing values could be out of date or missing. The close now redoes that month. While Stock Closing Value Month End Process is open, a background close that shows no progress for 30 minutes is also restarted automatically and carries on from its last checkpoint.

Opening the screen during a resumed close had the same problem. The screen now follows a resumed close to the end. It also shows a close that is queued but not started yet, so it can be followed or stopped.

saving, editing or re-posting a customer or supplier invoice now updates the customer or supplier statement much faster when that customer or supplier has a long history. On a large test database, re-posting an invoice for the customer with the longest history (about 69,000 statement documents) took about 2.4 seconds instead of about 12 seconds, and other customers and suppliers were about 26% to 36% faster. Statement figures and balances are unchanged, and this was checked after every test posting. The hotfix adds eight indexes to the statement tables. Building them takes under a minute during the update and needs some extra disk space: about 500 MB on the largest test database, and less on most.

The screen reported an error and stopped following the close, although the Process Manager still went on to finish it.