Browse By Tags

  • Issues opening Payroll 29.02 with a roaming profile created for a Windows server 2012 server

    We are having a very strange issues on our Server 2022 RDS server (21H2 Build 20348.2031) where users that were created back when we were using our old 2012 RDS server are unable to open Payroll version 29.02. The SBDdesktop.exe application appears in…

  • Sage 50 company files will not open from remote workstations after update to 2024, "Sage 50 cannot map the network share to a local drive path on the computer *servername*. Check the network share's registry information."

    Hello everyone, I just updated our server and a few users to the new Sage 50 Canadian 2024 update, and we are now experiencing an issue with opening company files from the server. We have 6 users that have a mapped drive on their local client that points…

  • Sage CRM: Updating a license

    After you have installed Sage CRM there will come a time when you will need to make changes to its settings. I don't mean the every day administrative changes like changing the security profiles or adding a new team. I mean big changes like needing…

  • Function library for tablescripts

    The code on this page was corrected 31st October 2009. Tablescripts are great, they allow you to add code to Sage CRM which will always fire when a table event happens, for example, the company is updated. Look in the developer/admin guides for more…

  • Controlling the Detached TableLevel Script Interval

    This article was updated 31st October 2009 to correct hyperlinks. Detached TableLevel Scripts are created in the same way as TableLevel scripts, except you select Detached Table Level from the Script Type list when completing the Table Script details…

  • You may need to recreate views manually

    Please note that this is not an exhaustive discussion and but simply represents the things that come to my mind when seeing this error. Why does it appear? The can be several reasons why this message appears and it usually comes when there has been…

  • What are current regedit or gpedit fixes to bypass MAPI popups CLICK TO RUN Office 365?

    These worked in the past (Outlook 2010), but are not fixing the popups this time around with Outlook 2016 via Office 365 (click to run install). (see pics) Also, in Outlook Trust Center, Programmatic access is set to "never warn me..." but apparently…

*Community Hub is the new name for Sage City