|
March 2016 - In This Issue:
|
|
|
|
Keeping In Touch
|
Time for a newsletter refresh!
In this issue we discuss new projects & considerations for deciding whether to upgrade Sage 100. The webinar will be of import to those who are interested in extending what data Sage 100 can capture through Custom Office, and the Tip of the Day will be helpful to those that use a different range of cheque numbers to denote online transfers.
Around our office, Robert has been working from Florida (much to our envy!), Shabnam is designing our new website, Kevin is working on bringing new functionality to Sage 100 with scripting, and Mark is back from a vacation to Portugal and Spain.
We're always looking for feedback, so please reply and let us know what you think of the new newsletter. |
|
 |
Current Projects
What We've Been Up To
Historical Tracking Do you want to track point in time values (inventory, open sales orders...) day-to-day or week-to-week, but without manually running reports and recording the values? Kevin has come up with a procedure to set up automated queries for tracking and retaining point in time values. We can also provide and design reports based on those values. This is dependent on running Sage 100 Premium, or version 2014 or later of Sage 100 Standard / Advanced.
Visual Cut Reports
Visual Cut ("VC") is our solution of choice for sending out automated reports from Sage 100. We can quickly set up schemes for sending you lists of daily invoices, customers hitting their credit limits, sales, quantities manufactured, etc.
Web Interfaces
Mark has been prototyping ways of setting up quick web-portals in-house for inputting information into Sage 100 from internal web pages, as opposed to giving every employee access to the programme. He's testing a number of approaches, depending on whether ProvideX or SQL versions of Sage 100 are being used.
Please reach out to us if any of this sounds like it could be of use to you, or you have other ideas you'd like to implement. Contact us!
|
To Upgrade or Not to Upgrade, That is the Question
|
We have seen a few trends that are worth mentioning.
First, Microsoft is actively pushing Windows 10 to PCs that have Windows 7 or Windows 8 installed. Windows 10 is only officially supported on Sage 100 v2016. There has been online chatter that v2015 will have an update that will make it officially supported, but we haven't seen anything yet. This is creating havoc for our customers who casually click the upgrade button without realizing the impact to their Sage 100 (and other business) software.
The second trend is that other software patches (Windows, anti-virus, and PDF converter updates) may conflict with Sage installed software or components.
Third is that Sage is releasing a new product each year, and issuing product updates only for the current version, and one prior. This means that if you are on v2016 or v2015, Sage is continuing to provide product updates. Earlier versions are not being updated. Yes, Sage is officially supporting earlier versions (see table below), but is limiting the level of support/assistance to those versions.
Since the release of v2013, upgrading your Sage 100 system has become less of a burden to clients and end users. We're able to do most of these upgrades remotely with minimal impact to end users. Given the speed of technology changes, it makes sense to stay on a current version. You're already paying your annual software maintenance payment to Sage; you should take advantage of the new features and technology changes that have been added.
|
Webinar Series What's Coming Up March 30:
Customization is one of Sage 100's most powerful features -- a major reason for choosing the product. Find out about Custom Office, and how you can capture, process and analyze more data essential to your business. You can add fields, make standard fields required, hide data on screens, and change system behaviour.
April 24:
Learn about Sage CRM and whether it can be a powerful asset for your sales force, or even just regular business as usual. It integrates with Sage 100, and there are cloud, mobile and on-site options available. Registration will be included in next month's newsletter.
Your support agreement with Munjal White entitles you to attend our webinars at no additional cost. We strongly encourage you to take advantage.
|
Tip of the Day A Separate Series of Unique Cheque Numbers
Some of our clients have been using different series of cheque numbers to indicate the difference in bank payments between cheques, and other payments such as EFT. For example, cheque #1300 is printed and used to pay a vendor, while cheque #700014 is a record in Sage 100 indicating a phone bill being paid from online banking. Say you have another phone bill to be paid, at cheque #700015, after having just printed a cheque at #1301. When you change the 'next' cheque number to #700015, sometimes Sage 100 will mark the entire range, from #1302 through #700014 as void. There is a utility to correct this, but perhaps it would be better to avoid the situation all together.
You can enable Wire Payments in Accounts Payable options which will enable a second series of numbers for your online vendor payments, without interrupting your cheque sequence. Please let us know if you would like further assistance with setting this up.
|
Quote to Ponder
"Appreciation is a wonderful thing: It makes what is excellent in others belong to us as well."
- Voltaire
|
|
|
|
|