Schulz Consulting

Consulting and Upgrades

  • Home
  • Services
  • Technical
    • Sage 100 New Features ( Brief )
  • Sage 100 Support

MAS 90 Trivia – just for fun

September 17, 2009 by Wayne Schulz

linked in mas90 trivia
Anyone for some Sage MAS 90 and MAS 200 trivia?

Jeffory M. Urquhart who is an ERP Implementation Specialist at Microliance in Florida has started an interesting trivia game over on LinkedIn that asks some tough but fascinating questions about MAS 90.

You’ll need to go way back with the product because Jeff’s questions are not for the beginner.

Jeff’s list of questions appear on the MAS 90 group on LinkedIn (click here to join first). This is not an official Sage forum, rather it’s a spot that fellow users and consultants can gather to exchange information, network — and even play the occasional game of MAS 90 trivia.

Here’s the list of MAS 90 trivia questions.

  1. What does M.A.S stand for?
  2. What did SOTA stand for?
  3. What was 09SAM?
  4. What  operating system platform was MAS 90 originally written for?
  5. When initially marketed, what was the application language that MAS 90 was written in?
  6. In the original versions, how were terminal IDs set?
  7. What year was MAS 90 introduced?
  8. What was the first version of MAS 90 for Windows?

What’s interesting is several long time Sage employees have added questions like the one Erika Jelovsek poses:

Ahhh, but if you really want to call yourself a historian of all things MAS 90 , you need to be able to define the acryonyms for these release names. And Craig, no jumping in right away…..let the non-Sage folks take a trip in the wayback machine to come up with these answers! ERBY, MERBY, LEFTY, IMSOPO, and, my personal favorite, TAMAN.

For the answers to these questions – and to read several more interesting tidbits of MAS 90 trivia – head over to the MAS 90 LinkedIn group. You’ll have to join the group but membership is free and you can leave anytime.

Link:

MAS 90 –  Trivia Just For Fun

Filed Under: Knowledgebase, Sage 100 ERP, Sage software Tagged With: craig jacobs, erby, erika jelovsek, imsopo, jeffory urquhart, lefty, mas200, merby, sage, Sage 100 ERP, sota, taman, trivia

Error 88 Sy_ReportEngine.pvc Line xxx [Solved]

September 4, 2009 by Wayne Schulz

dotmatrix.jpg

I’ve run into this on only a couple of occasions – most of the time in Sales Order.

The symptoms are an Error 88 SY_ReportEngine followed by a line #.

Other sales order forms should print correctly — the problem is usually just one form code — typically a packing list or shipping label.

Check to see that the printer is valid and that you can print other Crystal Forms.

If both of the above check out then I’ve successfully used the fix below:

Listed below is a copy of what SY_ReportSetting.m4t should look like. Yours will be a little different but the field names should be roughly the same.

For the purposes of this error message you only care about the last 4 or 5 fields .

Note that after a user incorrectly accessed the report (not able to track down the exact steps) that fields 38-41 were changed by MAS to bad values.

The values in the field below are what should be used.

Key=[S /O0000000006SO_SHIPPINGLABELS_UI.STANDARD ]
“ModuleCode:CompanyKey:ReportID:ReportSetting”

01 ModuleCode$………… [S/O]
02 CompanyKey$………… [0000000006]
03 ReportID$………….. [SO_SHIPPINGLABELS_UI]
04 ReportSetting$……… [STANDARD]
05 DefaultReport$……… []
06 Description$……….. [1 Across Plain]
07 SettingOptionsType$…. []
08 PrintReportSettings$… []
09 PrinterName$……….. [\\ACCT-KG\UPS THERMAL 2844]
10 SortReportBy$………. []
11 PageBreak$…………. []
12 Collated$………….. [Y]
13 ThreeHolePunch$…….. []
14 DateCreated$……….. [20061020]
15 TimeCreated$……….. [12.34951]
16 UserCreatedKey$…….. [0000000003]
17 DateUpdated$……….. [20061020]
18 TimeUpdated$……….. [12.59368]
19 UserUpdatedKey$…….. [0000000006]
20 NumberOfCopies……… 1.00
21 MultiPart$…………. [N]
22 TemplateDesc$………. [1 Across Plain]
23 Line1Message$………. []
24 Line2Message$………. []
25 EnableFax$…………. []
26 FaxSubject$………… []
27 FaxUseCoverPageFile$… []
28 FaxCoverPageText$…… []
29 FaxCoverPageFile$…… []
30 FaxBillCode$……….. []
31 FaxKeywords$……….. []
32 FaxHold$…………… []
33 FaxUseCreditCard$…… []
34 FaxSendOffPeak$…….. []
35 FaxUseHighResolution$.. []
36 FaxPrinter$………… []
37 FaxPriority………… .00
38 PaperOrientation……. 1.00
39 PaperSize………….. 1.00
40 PaperSource………… 15.00
41 PrinterDuplex………. 1.00

To correct this issue (only after you’ve ruled out the usual suspects like a problem with Crystal or bad print or corrupt form) — I’ve changed field #39 (which may be labeled with a different number) to 1.

In a support case I just had the number 258 was in field #39 instead of 1.

Changing the 258 to a 1 made the problem go away.

Requires familiarity with Data File Display Maintenance as well as a backup of your SY_ReportSetting.

This file is located in the SY_SYSTEM folder.

If any of this sounds scary or unfamiliar – contact your Sage Business partner.

Always backup first.

Filed Under: Knowledgebase, Sage 100 ERP, Tips and Tricks Tagged With: error 88, mas200, sage, Sage 100 ERP

How to show country names on forms using older MAS 90 and MAS 200 versions

July 30, 2009 by Wayne Schulz

mas90 country code information.jpg

To create country code on MAS90 and MAS 200 forms:

Earlier versions of MAS 90 and MAS 200 (typically prior to version 4.10 or 4.20) did not allow for easy linking of the country code name to the code itself.

While the country code could be placed on forms (Sales Orders, Purchase Orders, Checks) – the name of the country was not as easy to place for a few reasons –mainly that the data file required to pull the name from was not readily linkable.

Below is a workaround solution that you may find useful. It is primarily for MAS90 or MAS200 (it works on both) versions prior to 4.1 – so if you are using a later version you probably don’t need this procedure because Sage has wisely added country name to the tables that your forms are using.

All steps below require using Crystal Report Writer – which is included with your Sage MAS90 or MAS 200 product disks.

These are not beginner instructions – and assume some intermediate level comfort with Crystal Reports. Backup all your

For this example, assume that we are going to create a form for the ship to and bill to codes. The same logic here with slight modification can apply to any form with a bill/ship field.

Note: Technical information on creating a Crystal Sub report that shares variables is available from:

NOTE: Unfortunately links below to Crystal Reports technical documents appear to have been broken since Business Objects was acquired by SAP.

http://support.businessobjects.com/library/kbase/articles/c2007600.asp

1. Create a page header A that is above the main details (Note: It is important that this comes at the top of the page so that the shared variable calculates before the body of the report. If you do not put it at the top the whole thing doesn’t work). You will need to create a new header (Right click in the HEADER section area and select Insert Section Below. Once that section is created, right click on the section area again on the left side and select MOVE – then you can move it up).

2. Create a sub report for each Bill-To/Ship-To code. These will be placed into the page header created above.
a. Cty_ship
b. Cty_bill
c. Note: Link these back to the main table on the report. You’ll probably want to look in the Database – Visual Linking Expert to see what table is being used to hold your address information.

3. Within each of these subreports:

schulz mas90 country code1.jpg

a. Create a formula as follows (Note: Vary the variable name depending on whether you are creating a bill to or ship to)

b. Place the above formula in the body of the subreport in the details section. Once on the report, right click the formula, select format field, then font, change the font to WHITE (or any shade that won’t show on the report)

c. Place the SY_Country.CountryName in the body of the subreport in the details section. Change the font to white so it doesn’t print on the final report.

d. Leave the Details section viewable – all other sections should be suppressed – ie headers/footers. (Note: If you suppress the details section this won’t work – so be sure to leave it viewable. The way to get around seeing the data on the report is to later change the font to white and make the field very tiny).

e. Make sure your subreport is linked from the SO1_SOEntryHeader.ShipToCountry to the SY_Country.CountryCode

f. When you’ve placed both sub reports into the header section you created above, right click on each subreport and de-select the “can grow” checkbox. (Note: If you do not remove the check you may get a “page size exceeded” message)

4. Within the main report create two variables
a. Country_bill
b. Country_ship

schulz mas90 country code2.jpg

5. Now you can put this variable into your main report formula and the value from the subreport is carried over. The following is the example of it being worked into the @ship to address formula which is standard in the Sage SO Order and Invoice form.

6. Sample formula which has been modified with the new variable.

schulz mas90 country code3.jpg

7. Important: Place the new variables onto the report in the main header section (NOT the sub report) – you can make the white fonts so they don’t print. You must make them viewable (Cannot suppress or this does not work).

BACKGROUND NOTES ON THIS ISSUE:

Q: Client wants to display the Country Code in the forms (SO Orders, Invoices, Purchase Orders, Checks).

A: (Prior to version 4.1 and 4.2) There is no simple way to do this in MAS90/MAS200 — though there are two standard approaches.

The first approach to adding MAS90 country names on forms

Use Alias Tables — this would allow for a table to be used in a report more than once. You give each table an “alias” and it would then allow you to link it to separate fields. This would be needed for the Country Code field because it is potentially a different result for either the Bill To or Ship To.

The problem in MAS90 4.x+ with the Alias Tables is that there is a bug of some sort preventing them from linking to the SY_Country field. This is documented in the Sage KB with the workaround to use a subreport (an ok solution but the country name is impossible to properly line up since it is a free floating field).

The better solution is to use shared variables within the report. Basically this involves creating a new section (header) at the top of the report (important because the variable has to be created before the rest of the report). Then you declare the variables as shared and they can be read from the header on down to the main body.

I did this through the SO and it seemed to work.

Here is the link to the Crystal KB article showing how to create shared variables:

http://support.businessobjects.com/library/kbase/articles/c2007600.asp

On the subreport, you have to create a main subreport, a formula (put this on the subreport) and a shared variable (reference this on the main report).

In the main report you have to create a formula, call up the shared variable (see the Crystal KB for syntax) and then use it in the address formula. Do not forget to put the formula itself onto the form or the value won’t compute.

You want to make the font be white on white. Do NOT suppress and printing or the calculation does not work. If you make it very small you can hide it on the form.

IMPORTANT NOTE: This information is being made available “AS-IS”. Prior to making any changes on your system be sure you have a backup of all forms being modified.

Subsequent upgrades to MAS 90 or MAS 200 table structures may render some (or all) of these instructions obsolete. Sage may also fix bugs that we’ve referred to above. These instructions are meant to serve as a starting point for your own use – and not as a detailed step by step guide to resolving any particular issue. We take no responsibility for updating these instructions. We are not able to provide support (except for our own MAS 90 support clients) on implementing these instructions.

Filed Under: Crystal Reports, Hidden Options, Knowledgebase, Sage 100 ERP, schulz consulting, Tips and Tricks Tagged With: country code, Crystal Reports, forms, how to, mas200, sage, Sage 100 ERP, schulz consulting, Wayne Schulz

MAS 90 & MAS 200 Virtualization Guide Published

July 29, 2009 by Wayne Schulz

Virtualization allows you to allocate hardware resources among multiple virtual environments running on the same machine. Application virtualization is the use of software to allow multiple application images (such as Sage MAS) to run on the same hardware at the same time.

Sage has just issued their officially supported Virtualization configurations. This one page document (copy below for your convenience – be sure to check for updates as they become available) outlines the various virtualization platforms that may now be used to run both MAS 90 and MAS 200.

Benefits of Server Virtualization:

•Provision additional servers without investing in new hardware
•Run multiple operating systems and applications on the same physical server
•Increase the CPU utilization of an underutilized physical server by running multiple virtual environments
•Move virtual machines from one physical server to another without re-configuration
•Capture the entire state of a virtual machine and roll back to that configuration easily

Benefits of Workstation virtualization:

•Run multiple virtual machines on a single PC
•Quickly provision, deploy and reconfigure physical machines
•Run multiple operating systems and applications on a single PC
•Eliminate risk by creating isolated testing environment
•Built-in Snapshots and easy Restore capabilities

Filed Under: Hidden Options, Knowledgebase, Sage 100 ERP, Sage software, Technical Documents, Tips and Tricks Tagged With: ct mas90, hyper-v, mas200, sage, Sage 100 ERP, schulz consulting, terminal services, virtual pc 2007, virtualization, vmware, vmware server, Wayne Schulz, xenapp, xenserver

VMWare, XenApp, Virtual PC 2007, Terminal Services and Hyper-V now officially supported for Sage MAS 90, 200 and 500

July 24, 2009 by Wayne Schulz

Sage Software has provided some additional information on how their Sage MAS 90, 200 and 500 product are now officially supported on several virtual platforms.

A virtual platform is a way that computer users might for example run Microsoft Windows while also using an Apple MacBook Pro. These virtual software platforms have evolved from the early days where they were typically very difficult to get working reliably to present day where many companies are able to use virtual computers quite successfully.

virtualized MAS90 platforms.jpg

We use VMWare internally to run Sage MAS 90 on an Apple MacBook Pro as outlined in this post from May 2008.

We also have several clients using similar technology including one that integrates their iMac computer into the Windows network while running Sage MAS 90.

Filed Under: Knowledgebase, Sage 100 ERP Tagged With: "sage mas90", sage mas 200, sage mas 500

  • « Previous Page
  • 1
  • 2
  • 3
  • 4
  • Next Page »

Sage 100 Newsletter

Search Our Site

Sage 100 News

  • How to Fix: Sage 100 Desktop Launcher Closes Immediately After Login (No Error)
  • How To Update Sage Intelligence Keys as Sage Moves Away From Unlimited Licenses
  • Get More From Your Sage 100 Partnership
  • Sage Future 2025 Preliminary Agenda Released
  • Upgrading Sage 100 to 64-bit: Avoid These Integration Pitfalls
  • What’s New in Sage 100 2024? ( Video )
  • Sage 100 Users: Conquer Minnesota’s New Sales Tax & Delivery Fee Headache-Free
  • Elevate Your Sage 100 Expertise with SchulzSays: The Ultimate Newsletter for Users and Consultants
  • How To Purge Cleared Bank Reconciliation Transactions in Sage 100
  • 10 Exciting New Features in Sage 100 2024

Contact Us

Schulz Consulting · Connecticut Office · Available remotely nationwide.

Contact Schulz ConsultingPhone: 860-657-8544Email Us

We are a local branch of DSD Business Systems Connecticut.

Copyright © 2026 · Parallax Pro Theme on Genesis Framework · WordPress · Log in

Loading Comments...

You must be logged in to post a comment.