“Please, Sir, I want some more.” Granted, most of our Sage SalesLogix users are a bit better off than Oliver Twist, but there’s no denying that once you get a little bit of information, you inevitably want more. Of course, it sometimes feels about as hard as crossing the dining hall floor in front of everybody to ask for another helping. But, unlike an unscrupulous orphanage owner, we’re happy to ladle out more information. (As before, if the links are non-functional, use the link headings as search terms in the Knowledge Base)
Where’d my Write button go? It was right here!
This also comes up as “Why don’t I see a Write menu?”, so don’t panic just yet. If you’re not running Windows 7, you can skip down a little further, or keep reading to future-proof yourself against an inevitable upgrade headache.
In Windows 7, there is a handy little security feature called User Account Control. It was originally developed in response to the long held and often stated lament that Microsoft didn’t care about securing their operating system against malicious software. By and large, Microsoft has done right by their customers in this regard. However, when it comes to the Desktop Manager element of Sage SalesLogix’s Web Client, UAC stops being a general help and starts being a highly specific hindrance. There are four levels to UAC, arranged with a slider in the User Accounts section of the Windows Control Panel. The top of the slider is the most restrictive level of security, with the bottom essentially turning the security off. For Win7 users who want to install Desktop Manager, you’re going to want to turn UAC before you start the installation process, then turn it back on after you’ve configured Desktop Manager and verified it’s working properly. If you installed Desktop Manager with UAC on, the Write menu won’t show up.
For those of you running XP on your workstation, you’ve got it easy. If the Write menu is missing, a simple removal and reinstall will take care of things.
We’re about to do a hardware upgrade for our Sage SalesLogix server. What do we need to do?
In some respects, doing a hardware upgrade isn’t much different than an initial install. You’ll want to check minimum requirements, set up the service users, make sure you’ve got the right version of SQL or Oracle installed, and a lot of the other preparatory work that you did when you first got Sage SalesLogix. The key difference is that you’ve already got an existing database. Backing up and restoring the database is pretty easy. The only step that you really need to make sure gets done is to run the Sysdbafix_script.sql script against the database. This small SQL script can be found on your install disc or in the install package, usually in the Databases folder, though it may also be in the Upgrades folder. Once the script’s been run, you should be able to update your connections and datalinks and get back to business.
You know, our Sage SalesLogix version is kinda old. Maybe we should upgrade that, too.
Keeping up with the latest version of Sage SalesLogix is never a bad thing, but if it’s been a while between versions, trying to jump straight from an older version (say 6.2.3 for example) right to the latest and greatest (7.5.4, for the moment, though 8.0 is coming out soon) will be a very bad thing. For people, it doesn’t necessarily seem like such a big deal. For a computer, it’s the difference between the English found in Chaucer versus Stephen King. Internal systems get re-written or outright replaced. The methods that Sage SalesLogix uses to perform functions may differ significantly. Even the customizations that you had might be rendered inoperable. The only really safe way to upgrade if there’s a significant gap in versions is to upgrade iteratively. Make sure you’ve got all the Service Packs installed for your existing version, then move up to the next highest version, apply those Service Packs, and repeat until you’re up to your desired version. If you have customizations, you may want to verify those are still functional between steps up. And, as always, back up your databases before going through any sort of upgrade.