As the sophistication of mobile phones takes leaps and bounds, the mobile workforce is becoming more and more reliant on these devices. Where there was previously a laptop, now there may just be a single iPhone. While the raw power and features evolve, one thing that will not be changing for a long time is how big the device’s screen can be. This limitation can change how you see SageCRM on a mobile device. You might get a near desktop experience, but you’re zooming in, zooming out, scroll, scroll, scroll...Read More >
Data integrity checks in Sage 300 (formerly Accpac) are critical. It's easy to get the impression on how we, at BAASS Business Solutions, feel on the matter considering the number of times we bring it up. Data integrity checks can stop disasters before they start.
One of the down sides of data integrity checks, or a DIC as I like to call them, is that they can take a long time to run. Some larger databases can take hours, which is fine because you can continue working or walk away since it is going to just pop up with a nice report when it's done.
But oops, my workstation was set to print directly to the printer. The DIC is done, but instead of a nice report on my screen, Sage 300 is asking what printer to print to. I'm not going to print a 100 page report just to review it once and I don't want to run the DIC again. Is there something I can do? Yes!
The DIC creates a text version of this report and saves it to the Sage 300 shared data directory. To access this file, simply locate your Sage 300 shared data directory by going to Help -> System Information. Using Windows File Explorer, navigate to this path, then the COMPANY folder, followed by the folder where the name matches the database ID where you ran the DIC. Contained within, there should be a file called ERRORS.LOG. This file will be a full copy of the report you'd have received when the DIC was complete.
Not only does this save you grief if you missed the DIC report from Sage 300, but I actually prefer to read the report this way. Considering a great deal of the report is "0 Error(s) found", having it in text format allows you to quickly scroll through it.