====== Lime CRM Desktop Client 11.3.5189 ====== ; Product : Lime CRM Desktop Client ; Version : 11.3.5189 ; Date published : ; Platform : Windows ; Availability : [[https://builds.lundalogik.com/api/v1/builds/limecrm-desktop/versions/11.3.5189/file/|Manual installation]], [[https://builds.lundalogik.com/api/v1/builds/limecrm-desktop-reference/versions/11.3.5189/file|Reference]] Correction release for 11.3. It contains everything in [[releases:lpdc:11.3.4747|11.3.4747]] and the corrections below. 11.3.4747 was the final feature release of 11.3, so its release notes remain the description of what 11.3 contains. This release adds no new features. ===== Highlights ===== * **Changes to a document that is open for editing are no longer lost.** A document opened for editing in a program with tabs, for example Notepad++, could be checked in while it was still open. Later changes then stayed on the computer, and no message said so. The client now follows the program until it closes and uploads the changes when the document is no longer open. The document control shows the state of each document. Tools > Tracked documents lists every document that is open for editing or has changes that are not saved in Lime CRM. * **Save and close also uploads the documents of the card.** A document of the card that is open in another program is uploaded with what the program has saved. The document stays watched after the card closes. * **The client no longer freezes when a card opens.** In 11.3, the client could stop responding for good when a card opened, after the fields were shown and before the tabs and the action pad loaded. This is now corrected. * **A card no longer keeps changing its layout after the splitter is moved.** On some cards, for example a history with notes, the fields could start to flicker without end after the splitter was dragged, and the client had to be closed. This is now corrected. * **A card runs its VBA again when an action pad changes a field that the card does not show.** When an action pad changed a field through the web API and refreshed the card, the VBA of the card ran only if a visible field had changed. A card that sets its fields read-only from a hidden field, for example an end date, kept its old state until it was opened again. The card now runs its VBA whenever a field that the VBA reads has changed. * **Relation fields no longer show the record id instead of the name.** A relation field could show a text such as "company:117601" for the rest of the session. The client now loads the name again, and shows the id only while the name cannot be loaded. * **New keys to refresh a card.** CTRL+R refreshes like F5. SHIFT+F5 on a card loads the record again and runs its VBA and its action pad, also when nothing has changed. Unsaved changes on the card are kept. * **The client ends when the login window is closed.** Since 11.3.4494, Lime.exe could keep running in the background after the user closed the login window without logging in. The process now ends. * **VBA repairs itself for the user when it fails.** When VBA cannot start or cannot compile, the client now repairs the VBA registration of the user and asks the Lime Maintenance Service to repair the VBA registration of the computer. This targets the message "Failed to compile VBA." when it affects only some users of a database. * **Updates never restart the computer on their own, also in the VBA setup.** The [[releases:lpdc:11.3.4747|11.3.4747]] release notes promised this for every component. One case remained: the VBA setup could restart the computer without asking when Office held one of its files during an update. This is now corrected. * **The update service runs only current Lime setups.** An old release with a known problem can no longer be brought back and installed through the Lime Maintenance Service. * **Repair of a client for users without administrator rights.** TinyRepair is a new, separate download that installs the latest released client through the Lime Maintenance Service. * **VBA keeps working after a restart of Windows.** On some computers, VBA worked after an update but failed after the next restart with "One of the VBA components is missing or corrupt." This is now corrected. * **Records with a duplicated single relation open again.** When two related records pointed to the same record through a single relation, the record could not be opened. It now opens, and the relation field shows the problem and how to correct it. * **Lists always show columns.** A list could load its records but show no columns, or only one. The client now ignores stored views that contain no columns, and shows a default view when no view can be found. * **Sorting keeps working after a sort on a system field.** After a list was sorted on a field such as the created date, no other sort worked in that list. This is now corrected. * **Documents work again with older Lime CRM servers.** With a server from 2017 or earlier, documents could not be loaded. This is now corrected. * **Updates are faster.** An install or update no longer reinstalls VBA when VBA is already installed and correct. ===== Change log ===== ==== Security ==== * **The Lime Maintenance Service runs only installed modules and recently signed setups.** The service runs Lime-signed setups with full rights for any user. It now runs a setup only when the setup is part of a Lime installation on the computer, or when its signature carries a trusted timestamp that is at most 90 days old. A setup counts as installed only when standard users cannot change its folder. This extends the security hardening of the update service in [[releases:lpdc:11.3.4747|11.3.4747]]. * **Automatic updates are confirmed with the build server before installation.** Right before an update is installed, the client asks the build server again whether that version is still published in its channel. A version that was withdrawn is not installed, and its download is deleted. When the build server cannot be reached, nothing is installed in this session, and the update is offered again later. The client also checks the signature date of the update with the same 90-day rule as the service, so it no longer offers an update that the service would refuse. * **An install folder outside Program Files is protected.** When the client is installed in another folder, for example ''C:\Lime'' or a folder on ''D:'', the installer now sets the permissions of that folder: administrators and SYSTEM have full control, and standard users can read and run the files but not change them. An existing installation gets these permissions at its next update. Without them, the update service would not repair such an installation once its build is older than 90 days. Installations in Program Files do not change. * **Error reports of a failed data load no longer contain values from the query.** When data failed to load, the error report sent to Lime contained the SQL statement and the query with all values, for example a search text or a personal identity number. The report now contains only the query. Every value in it is replaced by a short code that cannot be translated back to the value, and the name of the filter is removed. Successful loads send nothing. ==== Improved ==== * **The client follows a document in the editing program until the program closes.** While the document is open in the program, saved changes are not uploaded, because the user is still working on it. The document counts as open when its name is in a window title of the program, when it is open in a tab of the program, or when the program holds the file open. Tabs are read through the accessibility interface of Windows (UI Automation). When the document has not been open and has not been saved for one minute, for example after its tab was closed, the client uploads the changes, releases the lock and keeps the file for the program. A later save takes the lock again. When the program closes, the changes are uploaded and the file is removed. When the client closes while the program runs, the changes are uploaded and the lock is released. A save that replaces the file, as some programs do, is also seen. * **The document control shows the state of the document.** Below "Open for editing", a line shows the state: for example "Being edited in Notepad++, uploaded when the editor closes", "Open in Notepad++, lock released, uploaded when the editor closes", "Saved in Lime CRM 10:32" or "Could not be saved in Lime CRM. The changes are on this computer." The line is information only. Its tooltip says that the document stays watched after the card closes. * **Tools > Tracked documents.** The menu lists the documents that were opened for editing in this session, with their state, and the documents that have changes on this computer from an earlier session. A click opens the record of the document. The menu ends with "Unsent documents...", which is no longer a separate item in the Tools menu. * **Save and close uploads the documents of the card that are open in another program.** The upload runs in the background, so the card closes at once. The tooltip of Save and close names the document and says that it stays watched and that the changes are uploaded when the program closes. * **Open for editing brings the program forward.** When the document is already open in a program, the program window comes to the front. Nothing is checked out or started again. When the document is in an inactive tab, the program is asked to show it. * **The list of unsent documents explains more reasons.** It now says when the server answered with an error, for example "The server answered with an error (HTTP 500)", and when the document could not be opened for editing because another user may have locked it. A forced unlock warns when changes on this computer are not saved in Lime CRM. * **The timing of the document watch can be changed.** An administrator can set ''LaunchWaitSeconds'' (default 10), ''PollSeconds'' (default 30), ''ReleaseGraceSeconds'' (default 60) and ''UseAutomation'' (default 1) in the database settings under ''Application\DocumentWatcher'', and per program under ''Application\DocumentWatcher\Processes\'', for example ''notepad++.exe''. ''UseAutomation'' 0 turns off the reading of tabs for a program. * **For VBA developers: document events and options.** The new event ''Database.DocumentActivity'' (''Document'', ''Activity'', ''Result'', ''Details'') reports when a document is checked out, checked in, could not be checked in, or released, whatever opened it. ''Document.OwnerRecordID'' and ''Document.OwnerField'' give the record and field that hold a document. ''lkCheckOutKeepLocal'' keeps the file on this computer when Lime CRM has a newer version, to replace that version with local changes. ''lkCheckInKeepLocal'' uploads the changes and releases the lock but keeps the file for a program that still has it open. * **The message says what to do when data fails to load.** The message "Failed to load data block." now includes a recommendation for the most common causes. Examples: the sign-in at a proxy in front of the server has expired, the network connection failed, the query took too long, or the user may not read a table. For a table the user may not read, the message names the table and says how to load the data now and how an administrator can give access. For an SQL error, it names the fields of the record type that have their own SQL expression, so that an administrator can check them in LISA. * **The message says what failed when VBA cannot start, and offers to start without the customizations.** When the VBA project of the database could not be loaded, the client stopped at login with only the VBA error. The message now says that the VBA project could not be loaded, whether a repair of VBA on the computer was requested, and what to do. It also asks if the client should start without the customizations. No is the default and closes the client, as before. Yes starts the client with an empty VBA project. That project can never be saved, so it cannot replace the VBA project of the database. * **The tooltip of a relation field explains a relation that has more than one related record.** See the Fixed section. The technical tooltip (SCROLL LOCK) of every relation field also shows whether the relation is single or multiple, and in which table its key is stored. * **Per-user repair of the VBA registration.** Before the VBA project opens, the client checks the registration of VBA, the MSForms controls and the OCX controls that Lime installs, in the part of the registry that belongs to the user. Entries that point to a missing file are removed. After a failed start or compile, the next start also removes per-user entries of the MSForms controls that point to another copy of ''FM20.DLL''. Before the client changes anything, it saves the entries to a backup file in ''%LOCALAPPDATA%\Lundalogik\Lime\VbaRepair'', which restores them by double-click. When the backup cannot be written, nothing is changed. When VBA could not be compiled, the client says that it repairs the registration at the next start, and VBA error messages offer a restart. This happens only once. When VBA still does not compile after the repair, the cause is probably in the VBA project itself, and the client does not offer the restart again. * **Repair of the VBA registration of the computer after a failure.** Earlier, the client started the VBA setup only when the VBA component was missing. It now also asks the Lime Maintenance Service to run the VBA setup when VBA fails to start or to compile, at most once an hour per user. The request does not delay the start of the client. * **The VBA setup checks more of the registration.** The VBA setup now checks every MSForms control and both MSForms type libraries against the ''FM20.DLL'' of Windows, and checks and repairs all 24 compatibility aliases of the VBA controls. * **The client handles the VBA form cache files with more care.** VBA keeps cache files (''.exd'') for the controls that a project uses. A damaged cache file can prevent the project from compiling. The client deleted every cache file it found at every start. It now checks the cache files before the project opens, keeps the files that worked at the last successful compile, and deletes only files that changed or are unknown. When a file cannot be deleted, the error report names the program that holds it. * **The client no longer writes compatibility aliases for VBA controls at every start.** The VBA setup already writes them for the computer. The client wrote a copy in the registry of each user at every start, which could hide a later repair of the computer. * **TinyRepair repairs a client for users without administrator rights.** A user without administrator rights cannot run the client installer, and a damaged client cannot always update itself. TinyRepair downloads the latest released client from Lime, checks that it is signed by Lime Technologies, and lets the Lime Maintenance Service install it. An older client is upgraded and the same version is repaired. A newer client is never downgraded. When the service is stopped and the user is allowed to start it, TinyRepair starts it. TinyRepair writes each step to its window and to ''%LOCALAPPDATA%\Lime\TinyRepair.log''. Download: [[https://builds.lundalogik.com/api/v1/builds/limecrm-tinyrepair/versions/latest/file|TinyRepair]]. * **The update you agree to install is the version that is recommended now.** When you choose to install an update, the client first asks the build server which version is recommended now. It waits at most 10 seconds. When another version is recommended, nothing is installed. The client downloads that version and tells you that it replaces the update. When the build server does not answer, the check before installation decides, as before. When a regular check finds that no update is recommended any more, the downloaded update and its notification are removed. * **Update downloads that are no longer needed are removed.** The client keeps update downloads in ''%TEMP%\Lime\AutoUpdate'' between sessions. At start it now removes the downloads of the installed version and of older versions. Each answered update check also removes downloads of versions that are no longer recommended. Earlier, these files stayed until the next update was complete. * **Better error reports when VBA fails.** The report of "Failed to compile VBA." now states which repairs the client made and the state of the VBA registration. When a VBA-related component is not registered, the report names it. * **Install and update no longer reinstall VBA when it is correct.** Every install or update uninstalled and installed VBA 7.1 and the Visual C++ 2010 runtime again, which could take more than two minutes. The client starts again after an automatic update only when this step is complete. The VBA setup now checks VBA 7.1, its controls, licenses and aliases first, and reinstalls VBA only when a check fails. It installs the Visual C++ 2010 runtime only when ''msvcr100.dll'' or ''msvcp100.dll'' is missing or older than the current version. A repair of the client still reinstalls VBA completely. * **An expanded section on a card scrolls into view.** When you expand a section, the card scrolls so that the section header and its fields are visible. A section that is taller than the card is scrolled so that its header is at the top. Sections expanded from VBA, and sections restored when a card opens, do not scroll. * **A stored view or filter with content that does not belong in it is not offered.** A stored view can contain filter conditions among its columns. Such a view loaded its records but showed no columns, or only some, and it still appeared in the list of views. When a view loads, the client now keeps only its columns. A view without columns, and a filter that contains anything other than conditions and And, Or and Not, are not shown in the list of views or filters. They remain on the server. The error report to Lime names each view or filter that was left out. * **A list shows a default view when it has no view to show.** When no view could be found for a list, for example when the specified view was missing, the list showed no columns. The client now shows a default view with the fields of the record type, for all users. The automatic view "[Standard]" is now also created for a tab that shows only views of its record type and has no views of its own. * **The update notification is shorter and shows the versions.** The notification of an available update now reads, for example, "Lime CRM Desktop 11.3.5189 is available, click here to upgrade from 11.3.4747. What's new?". It no longer says that the user accepts the license agreement by upgrading. The text is the same in English, Swedish, Danish, Norwegian, Finnish and French. * **CTRL+R refreshes.** CTRL+R now does the same as F5 in every window, also when an action pad has the focus. * **SHIFT+F5 forces a refresh of a card.** On a card, SHIFT+F5 loads the record again and always runs the ''Controls.AfterLoad'' and ''Controls.Refresh'' events and the action pad, also when no field has changed. Unsaved changes on the card are kept. In lists, SHIFT+F5 works as before. * **The reference installation is a smaller download.** The ZIP file of the reference installation is now compressed. It is about half the size, for example 76 MB instead of 146 MB. The files in it do not change. * **A refresh also loads the fields that a card does not show.** When a card or VBA refreshes a record, the client now also loads the simple fields of the record that are not shown, in the same request. Simple fields are fields of the record's own table without an SQL expression, such as text, numbers, dates, yes/no and options; relations, documents and long texts are not included. VBA that reads such a field after a refresh now gets the current value. A field with an unsaved change is not loaded again, so the change is kept. * **Better diagnostics when a card does not refresh.** When an event does not reach its handler, the client writes a line to the debug output and sends an error report to Lime once per kind of event. The refresh of a card also writes a line for each step where it stops, with the names of the changed fields but never their values. These lines can be captured with DebugView. ==== Fixed ==== * **A document in a program with tabs was checked in while it was still open.** Notepad++ shows only the active tab in its title. When the user changed tab, the client treated the document as closed, checked it in and stopped watching it. Later saves in that tab never reached Lime CRM. The client now reads the tabs of the program and watches the document until the program closes. * **A failed upload is no longer silent.** When the upload of a document failed, the changes stayed on the computer, and only a line in the log said so. The document control now shows the failure, and the document is listed in Tools > Tracked documents and in the list of unsent documents. When the client uploads a document by itself, for example after the program closed, and the upload fails, the list of unsent documents opens. * **Changes on this computer never overwrite a newer save by another user.** When changes on this computer are uploaded later, the client first compares the version in Lime CRM with the version it last received. When another user saved or locked the document in between, the changes are kept on this computer and listed as unsent, and the document is not opened over them. * **''Document.CheckIn'' with ''lkCheckInKeepCheckedOut'' deleted the file.** The changes were stored, but the file on this computer was deleted. A program that does not hold the file open lost it, and with Word the check-in reported an error although the changes were stored. The file is now kept, and the document stays checked out. * **The lock could be lost without a word after an upload.** The server releases the lock of a document at every upload, and the client takes it again. When that failed, the client still showed the document as locked by the user. The document now shows as released, and a later save takes the lock again only when no other user has changed the document. * **The lock filters and the lock view work for templates.** "[Locked by me]", "[Locked]" and the lock view were not available for templates, because the client looked for the lock fields under the name of the document field instead of the name of the record type. The client now finds them for every record type with a document field. * **The client could watch a program of another user.** On a computer with several users, for example a terminal server, the check that a program belongs to the same user compared invalid memory. The check now compares the user correctly. * **A card no longer keeps changing its layout after the splitter is moved.** On a card with a text field that fills the remaining height, for example the notes of a history, the card could switch between two layouts without end after the splitter between fields and tabs was dragged. The card could not be used, and the client had to be closed. The field measured its text from its current size instead of from the size the layout offered, so each layout caused the other one. The field now measures its text at the offered width, so one size always gives one layout. As a last protection, the card stops changing its layout by itself after three changes without mouse or keyboard input. * **The client ends when the login window is closed.** Since 11.3.4494, when the user closed the login window without logging in, Lime.exe stayed in the list of processes and had to be ended in Task Manager. The embedded browser of the login window was not released before the process ended, and Windows then waited for it without a time limit. The client now releases the embedded browser on every way the client ends. * **Search dialogs from VBA show the name of the record.** A search dialog opened from VBA without a view, for example a picker in a solution, used the personal view of the list ("My view"). When that view did not contain the field that names the record, the rows could not be told apart, and the quick filter found nothing. The dialog now uses the stored search view, then "[Search]", then "[Standard]", and otherwise a generated view that starts with the field that names the record. A personal view is no longer used, as before 11.2.3872. * **The search settings stay available in a search dialog that loads its records at once.** In a dialog opened with ''AutoLoad'', the button for the search settings was hidden. It is now shown at the lower left, beside the other buttons, and closing the settings loads all records again. An administrator can also open the settings with the keyboard shortcut of the button when the dialog was opened with ''DisableAdvanced''. Nothing changes for other users. * **Sorting keeps working after a sort on a system field.** In 11.3, when a list was sorted on a system field, for example the created date, the sort was stored incorrectly with the view. After that, no other sort worked in the list. This is now corrected. * **Documents load from older Lime CRM servers.** Lime CRM servers from 2017 and earlier have no size column for files. With such a server, the client could not load documents. The client now checks if the column exists, and loads documents without the size when it does not. * **A text field emptied by drag and drop is saved.** In 11.3, when you moved all text from a field to another field with drag and drop, the emptied field was not saved. The old value came back when the record was loaded again. The change is now saved. * **The sort arrow stays visible beside long column names.** A long column name could push the sort arrow out of sight. The arrow is now placed after the name, or at the right end of the column header with the name shortened. The arrow follows the font size and the screen scaling. * **The splitter between fields and tabs follows the card when a section expands or collapses.** After a section was expanded, the splitter stayed at the old height of the card. It now moves with the content. Cards with fields of variable height behave as before. * **A web login no longer removes the cookies of other sites.** Before each web login, the client removed every cookie of the shared browser profile, also those of an identity provider and those of a login in another Lime window. On the first login in a session, the cookies were not removed at all. The client now removes only the cookies of the server it logs in to, and always before the login page opens. * **Template Manager shows templates in all folders after it is opened again.** When Template Manager was opened a second time in the same session, it used the folders and tables from the first time. Templates in a newer folder were not shown until the client was restarted. A click in the icon list with no icon selected also showed "An unexpected error has occurred". Both are now corrected. * **Saving a new record no longer makes extra calls to the server.** After each save, the client checked whether the record of the active user had changed. For a new record of any type, for example a new document, this check asked the server for a permanent id. The client now compares the record type first and makes no call to the server. * **Mass update reloads the right records.** The reload after a mass update read the records of the list on a background thread. It now takes the records before the update starts, so the right records are reloaded also when the filter changes during the update. * **The update notification no longer stays on "Downloading".** From the second update check in a session, the notification showed "Downloading" and was never replaced. This also happened when the download failed or when the update service would refuse the setup, and the notification then stayed for up to 24 hours. A completed download now always replaces the notification. When a download fails or is refused, the update that was offered before is offered again. When there is no such update, the notification is removed. A download from an earlier session is offered right after the first check, without the "Downloading" notification. * **Reports show texts again for option, link, set and yes/no fields.** Since 11.3, a field formula in LimeReports, and ''Record.Eval'' with ''lkEvalTypeAuto'', returned the stored value of these fields, for example an option key or a record id, where 11.2 returned the text. They return the text again. * **The client could stop responding while a document was saved.** When the modified state of a document changed on a background thread while the window was painted, both could wait for each other. This no longer happens. * **The client closes properly when Windows signs out or restarts.** When Windows ended the session, the client unloaded VBA without its normal shutdown sequence. This could make the client crash during sign-out or restart. The client now runs the same shutdown sequence as when it is closed. * **SHIFT+F5 refreshes the list also when the filter or view cannot be reloaded.** SHIFT+F5 first reloads the filter and the view from the server. When that failed, for example for an ad hoc filter or after the session had expired, the list was not refreshed and an error was shown. The list is now refreshed anyway. The refresh button with SHIFT now does the same as SHIFT+F5. * **Action pads can read ''ActiveExplorer.Classname'' again.** In 11.3, an action pad that used Lime Bootstrap could read only ''ActiveExplorer.ClassName''. Action pads that check ''Classname'' lost menus and buttons that depended on it. Both names now work, as in 11.2. * **An action pad in an inspector could stay empty.** In some cases the embedded browser of an action pad was never started when the inspector was shown. The client now starts it when the pane is painted without one. * **''Record.Format'' keeps an unfinished placeholder as text.** A placeholder without its closing character, for example ''A