Minotaur Software Ltd
 
General Ledger
Accounts Receivable
Accounts Payable
Invoice / Order Entry
EDI
Inventory
Lot/Serial Control
Beverage
Chemical
Food
Manfacturing
Meat
Advanced Reports
Canadian Payroll
CRM
Point of Sale
Home
Software
Implementation
Newsletter
The Minotaur Team
Testimonials
Case Studies
User Conference
Request Info
Request Demo
Contact Info
Contact Info
 
Volume 14 Issue 1 - March 2005
Out of the Maze
A Publication of Minotaur Software Ltd.
 
10. Run a Check Summarized GL Report and compare to the earlier Check Summarized GL Report. The two reports should look the same except that the new report will have a series of additional lines similar to the following:

Date     Inve     0.00     Missing     Account

Where Date will be a valid date and Account will be a valid general ledger account.

These lines represent instances where there are records in GLREC that total to 0.00 in native account currency but for which there is no zero record in SUMREC. As this is exactly the change we are implementing, any such records are probably appropriate. The more such records you see, the more likely you are to see an improvement in the speed of your financial reporting. At some point in the future we will likely modify the Check Summarized GL Report so that it no longer lists these occurrences, but that system change is not yet available.

Again, if there are changes beyond these missing zero records, it will be necessary to decide whether or not those changes are appropriate and how to manage them.


11. If there are no issues to be addressed, allow users back into the system.

We would recommend that you allow significant time to process the steps outlined above. The partner outlined above that experienced a 75% improvement in the speed of their balance sheet found that it required approximately 14 hours to complete this process. Of course, the time you require will be dependent on the number of foreign currency transactions in your Minotaur system since its inception.

It should be noted that the process outlined above is entirely optional. While the outlined change will provide some users with dramatic speed improvements in their financial reporting and exchange rate changes, you may decide that you do not require those improvements. If that is the case, there is no need for you to reload your summarized GL transactions.

Conversion to MBS6.2 for Development By Victor Boersma

As most of you are aware, in 2004, Minotaur introduced our new MBS6.2 GUI client to replace the older MBS6 GUI client. As usual, the change is only to the user interface, the basic programs accessed by the user interface remain unchanged.

MBS6.2 uses Java 4 technology instead of the Java 3 technology used by MBS6. As such, it can provide a number of new features such as icons and an address bar. As well, it takes advantages of a number of bug fixes provided by the makers of Java which are only available in the later versions of Java.

When we first introduced MBS6.2 in 2004, users that implemented the product identified a number of issues with the new product that could stand some improvement. At this time, we believe we have addressed most of these issues - with the notable exception of ghost boxes which only occur on a certain few workstations and for which there is a known workaround.

It should be noted that there are of course differences between the way MBS6.2 and MBS6 work. Generally, these minor differences are expected and offer an overall improvement to the system. Of course, users that are familiar with the MBS6 client may find those differences awkward when they are first introduced. We believe you will find that this is simply a training issue and once users become familiar with the MBS6.2 client, will not present any obstacle to efficiently processing your Minotaur system.

Accordingly, we have made a decision to discontinue development on the MBS6 platform. As changes are introduced to the Minotaur system, we will ensure that they function appropriately with the MBS6.2 client. In general, this will usually mean that they also function properly with the MBS6 client. However, if there is a problem with the MBS6 client, we will generally not do extra programming and testing to correct those problems.
Users of MBS6 will probably find that in the short term, this decision will have no effect for you. However, we expect that in the longer term, you may start to see new Minotaur functionality which you cannot take advantage of due to the fact that you are using the older client. In those instances, we will of course suggest that you upgrade to the MBS6.2 client.
Page1 Page2 Page3 Page4 Page5