Sage 100

Does anyone know what file I can edit to remove old items from the Sage Installed Modules List? There are some 3rd party mods that don't uninstall properly, if at all.

------------------------------
Mary Mays
Professional Software, Inc.
------------------------------

short answer: I don't know where the listing gets its info.
long answer: Removing mods from the listing but not the product, they may come back to bite you, yet. Even if you didn't re-install them after upgrading.  But that said, I know there is info in the Links folder and I've renamed it to resolve certain issues.  

Here's something on that topic. 

Sage 100 (formerly Sage MAS 90 or 200) versions 4.00 through 4.50; and 2013 and higher:

1. Open Modules, Library Master, Reports menu, Installed Modules Listing
2. Check the modules listed for non-standard MAS 90 or 200 programs, asterisks by the modules, or level numbers that are not consistent with the existing level number.

MAS 90 or 200 versions 3.71 and earlier:

1. Open Modules, Library Master, Utilities menu, Installed Applications Listing
2. Check the applications listed for non-standard MAS 90 or 200 programs, asterisks by the modules, or level numbers that are not consistent with the existing level number.

To check whether a third-party module may be activated for specific companies:

1. Open Library Master, Main menu, Company Maintenance
2. For Company Code, select a company
3. In the Activated Modules area, check for any non-standard application modules.

Program files added by third-parties:

• The "..\MAS90\Links" folder (on the server where Sage 100 is installed) may contain third-party program files other than Default.pvc. Any program file in that directory other than Default.pvc indicates existence of third-party program enhancement(s).
  • Note: Not all third-party developers follow this rule. A Sage 100 system with only Default.pvc in the "..\MAS90\Links" folder may still be modified, with third-party developers directly replacing standard Sage 100 program files in other folders/directories. In other words:
    • If the problem no longer occurs after files in the "Links" folder are temporarily removed, then that would prove the issue is due to third-party modification.
    • However, if the problem still occurs after files in the "Links" folder are temporarily removed, that does not prove the issue is not due to third-party modification.
  • Note: Third-party enhancements for Legacy (non-Business Framework) application modules typically do not use the "Links" folder.
• Standard Sage 100 Business Framework program files typically do not have numbers in their file names. Sometimes third-party developers use numbers in program file names: It could be their developer code, or it could be a catalog or product number (for their software product), etc.
  • If an error message occurs with a program file that is not a standard Sage 100 program file, then it is likely a third-party program issue.
  • The SY_Developer.m4t data file contains a list of records, each with a 3-digit DeveloperCode key, and a second field, DeveloperName. If you have a program with a number in it, that may correspond to the code of the developer.

------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

------Original Message------

short answer: I don't know where the listing gets its info.
long answer: Removing mods from the listing but not the product, they may come back to bite you, yet. Even if you didn't re-install them after upgrading.  But that said, I know there is info in the Links folder and I've renamed it to resolve certain issues.  

Here's something on that topic. 

Sage 100 (formerly Sage MAS 90 or 200) versions 4.00 through 4.50; and 2013 and higher:

1. Open Modules, Library Master, Reports menu, Installed Modules Listing
2. Check the modules listed for non-standard MAS 90 or 200 programs, asterisks by the modules, or level numbers that are not consistent with the existing level number.

MAS 90 or 200 versions 3.71 and earlier:

1. Open Modules, Library Master, Utilities menu, Installed Applications Listing
2. Check the applications listed for non-standard MAS 90 or 200 programs, asterisks by the modules, or level numbers that are not consistent with the existing level number.

To check whether a third-party module may be activated for specific companies:

1. Open Library Master, Main menu, Company Maintenance
2. For Company Code, select a company
3. In the Activated Modules area, check for any non-standard application modules.

Program files added by third-parties:

• The "..\MAS90\Links" folder (on the server where Sage 100 is installed) may contain third-party program files other than Default.pvc. Any program file in that directory other than Default.pvc indicates existence of third-party program enhancement(s).
  • Note: Not all third-party developers follow this rule. A Sage 100 system with only Default.pvc in the "..\MAS90\Links" folder may still be modified, with third-party developers directly replacing standard Sage 100 program files in other folders/directories. In other words:
    • If the problem no longer occurs after files in the "Links" folder are temporarily removed, then that would prove the issue is due to third-party modification.
    • However, if the problem still occurs after files in the "Links" folder are temporarily removed, that does not prove the issue is not due to third-party modification.
  • Note: Third-party enhancements for Legacy (non-Business Framework) application modules typically do not use the "Links" folder.
• Standard Sage 100 Business Framework program files typically do not have numbers in their file names. Sometimes third-party developers use numbers in program file names: It could be their developer code, or it could be a catalog or product number (for their software product), etc.
  • If an error message occurs with a program file that is not a standard Sage 100 program file, then it is likely a third-party program issue.
  • The SY_Developer.m4t data file contains a list of records, each with a 3-digit DeveloperCode key, and a second field, DeveloperName. If you have a program with a number in it, that may correspond to the code of the developer.

------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

Let's see, the reports comes from a work file.  The workfile is probably made from these tables.  Sy_Module?

SY_Activation . . . . . . . . . . . . . SY Activation
 SY_ActivationReq. . . . . . . . . . . . SY Activation Requirements
 SY_ActivityLog. . . . . . . . . . . . . SY Activity Log
 SY_ActivityLogReportWrk . . . . . . . . SY Activity Log Report Work
 SY_ActivityType . . . . . . . . . . . . SY Activity Type
 SY_BaseODBCSecurity . . . . . . . . . . SY Base ODBC Security
 SY_BatchManager . . . . . . . . . . . . SY Batch Manager
 SY_Broadcast. . . . . . . . . . . . . . SY Broadcast
 SY_ClassEnhancement . . . . . . . . . . SY Class Enhancement
 SY_Company. . . . . . . . . . . . . . . SY Company Master
 SY_CompanyListingWrk. . . . . . . . . . SY Company Listing Work
 SY_Console. . . . . . . . . . . . . . . SY Console
 SY_Context. . . . . . . . . . . . . . . SY Context
 SY_ContextAFM . . . . . . . . . . . . . SY Context Advanced Field Mappings
 SY_ConversionDriver . . . . . . . . . . Conversion Driving Records
 SY_ConversionHistory. . . . . . . . . . System Conversion History
 SY_Country. . . . . . . . . . . . . . . SY Country Master
 SY_CreditCardProcessXref. . . . . . . . SY Credit Card Process Xref
 SY_CreditCardRestart. . . . . . . . . . SY Credit Card Restart
 SY_CrystalAnalysisWrk . . . . . . . . . SY Crystal Analysis Work
 SY_Deferred . . . . . . . . . . . . . . Deferred Printing Master
 SY_Developer. . . . . . . . . . . . . . SY Develope
 SY_DeveloperManifest. . . . . . . . . . Developer Manifest
 SY_Dialog . . . . . . . . . . . . . . . SY Dialog
 SY_DialogSettings . . . . . . . . . . . SY Dialog Settings
 SY_DictionaryConversionHist . . . . . . Dictionary Conversion History
 SY_EBusinessManagerUserID . . . . . . . SY EBusiness Manager User ID
 SY_EISViewMaster. . . . . . . . . . . . SY EIS View Master
 SY_EmbeddedIOSettings . . . . . . . . . SY EmbeddedIOSettings
 SY_Enhancement. . . . . . . . . . . . . SY Enhancement
 SY_EnhancementModule. . . . . . . . . . Enhancement Level Info
 SY_ExportLink . . . . . . . . . . . . . Export Link
 SY_ExtendedSolutionUDFConvWork. . . . . SY Extended Solution UDF Conversion Work
 SY_FieldMapping . . . . . . . . . . . . SY Field Mapping
 SY_FinancialReport. . . . . . . . . . . GL  FinancialReport
 SY_FinancialReportColumn. . . . . . . . Financial Report Column Mapping
 SY_FinancialTerminology . . . . . . . . Default Financial Terminology Descriptions
 SY_FormsEFilingVersion. . . . . . . . . Forms eFiling Version
 SY_GridDefinition . . . . . . . . . . . Grid definition
 SY_InstalledModulesListingWrk . . . . . SY Installed Modules Listing Work
 SY_JournalErrorLogWrk . . . . . . . . . SY Journal Error Log Work
 SY_LastFormUsed . . . . . . . . . . . . SY Last Form Used
 SY_LinkPathsWork. . . . . . . . . . . . SY _Link Paths Work
 SY_LockFiles. . . . . . . . . . . . . . SY Lock Files Reference
 SY_MemoDefault. . . . . . . . . . . . . SY Memo Default
 SY_MemoManager. . . . . . . . . . . . . SY Memo Manager
 SY_MemoRelationship . . . . . . . . . . SY Memo Relationship
 SY_MemoSettingsListingWrk . . . . . . . SY Memo Settings Listing Work
 SY_Menu . . . . . . . . . . . . . . . . SY Menu
 SY_Message. . . . . . . . . . . . . . . Messages
 SY_Metering . . . . . . . . . . . . . . Metering
 SY_Module . . . . . . . . . . . . . . . SY Module
 SY_ModuleDate . . . . . . . . . . . . . Module Access Date
 SY_ModuleDateListingWrk . . . . . . . . SY Module Date Listing Work
 SY_MultiPartForm. . . . . . . . . . . . SY Multi Part Form
 SY_NoMessage. . . . . . . . . . . . . . SY No Message
 SY_ODBCSecurity . . . . . . . . . . . . SY ODBC Security
 SY_PaymentCenterReference . . . . . . . Payment Center Access Reference
 SY_PayrollEFilingMapping. . . . . . . . Payroll EFiling Mapping (PIM)
 SY_PeriodEndListingWrk. . . . . . . . . SY Period End Listing Work
 SY_PeriodEndReport. . . . . . . . . . . Period End Report
 SY_Personalize. . . . . . . . . . . . . SY Personalize
 SY_PersonalizeALE . . . . . . . . . . . SY Personalize ALE
 SY_PollingSystem. . . . . . . . . . . . SY Polling System
 SY_PopupItem. . . . . . . . . . . . . . Popmenu Item
 SY_PopupMenu. . . . . . . . . . . . . . Popup menu Menus
 SY_PopupMenuItem. . . . . . . . . . . . Popup menu item
 SY_PopupXref. . . . . . . . . . . . . . Popupmenu panel Xref
 SY_PreMigrationCompany. . . . . . . . . SY Pre Migration Company
 SY_PreMigrationItemCode . . . . . . . . SY Pre Migration Item Code
 SY_PreMigrationWarehouse. . . . . . . . SY Pre Migration Warehouse
 SY_PrinterPreferences . . . . . . . . . SY Printer Preferences
 SY_ProcessFlows . . . . . . . . . . . . Process Flows
 SY_RebuildLog . . . . . . . . . . . . . SY Rebuild Log
 SY_Relation . . . . . . . . . . . . . . SY Relation
 SY_ReportManagerFormat. . . . . . . . . SY Report Manager Format
 SY_ReportManagerMaster. . . . . . . . . SY Report Manager Master
 SY_ReportManagerTemplate. . . . . . . . SY Report Manager Template
 SY_ReportOption . . . . . . . . . . . . Report Option
 SY_ReportSelection. . . . . . . . . . . Report Selection
 SY_ReportSetting. . . . . . . . . . . . SY Report Setting
 SY_ReportSettingsListingWrk . . . . . . SY Report Settings Listing Work
 SY_ReportWizardExpressions. . . . . . . SY Report Wizard Expressions
 SY_ReportWizardFields . . . . . . . . . SY Report Wizard Fields Used
 SY_ReportWizardFilters. . . . . . . . . SY Report Wizard Filters
 SY_ReportWizardGroups . . . . . . . . . SY Report Wizard Groups
 SY_ReportWizardLinks. . . . . . . . . . SY Report Wizard Links
 SY_ReportWizardMain . . . . . . . . . . Report Wizard main file
 SY_ReportWizardRoles. . . . . . . . . . SY Report Wizard Roles
 SY_ReportWizardSorts. . . . . . . . . . SY Report Wizard Sorts
 SY_ReportWizardSources. . . . . . . . . SY Report Wizard Sources
 SY_ResourceRoleSecurity . . . . . . . . SY Resource Role Security
 SY_Role . . . . . . . . . . . . . . . . SY Role Master
 SY_RoleReportODBCSecurityWrk. . . . . . SY Role Report ODBC Security Work
 SY_RoleReportWrk. . . . . . . . . . . . SY Role Report Work
 SY_RoleSecurity . . . . . . . . . . . . SY Role Security
 SY_SagePEP. . . . . . . . . . . . . . . Sage Product Enhancement Program - key/value pairs
 SY_SagePEPSettings. . . . . . . . . . . Sage Product Enhancement Program - Settings
 SY_SagePEPTask. . . . . . . . . . . . . Sage Product Enhancement Program - Track Tasks
 SY_SagePEPTrack . . . . . . . . . . . . Sage Product Enhancement Program - Track Data/Events
 SY_SalesTaxClass. . . . . . . . . . . . SY Sales Tax Class
 SY_SalesTaxCode . . . . . . . . . . . . SY Sales Tax Code
 SY_SalesTaxCodeDetail . . . . . . . . . SY Sales Tax Code Detail
 SY_SalesTaxCodeListingWrk . . . . . . . SY Sales Tax Code Listing Work
 SY_SalesTaxSchedule . . . . . . . . . . SY Sales Tax Schedule
 SY_SalesTaxScheduleDetail . . . . . . . SY Sales Tax Schedule Detail
 SY_SalesTaxScheduleListingWrk . . . . . SY Sales Tax Schedule Listing Work
 SY_SalesTaxScheduleStateXRef. . . . . . SY Sales Tax Schedule State XRef
 SY_SalesTaxScheduleZipXRef. . . . . . . SY Sales Tax Schedule Zip XRef
 SY_SampleAccounts . . . . . . . . . . . SY SampleAccounts
 SY_SampleAccountsWrk. . . . . . . . . . SY Sample Accounts Work
 SY_SQLOptimize. . . . . . . . . . . . . SY SQL Optimize
 SY_StarShipWork . . . . . . . . . . . . StarShip Work File
 SY_State. . . . . . . . . . . . . . . . SY State Code Master
 SY_Surrogate. . . . . . . . . . . . . . SY Surrogate
 SY_SurrogateLog . . . . . . . . . . . . SY_SurrogateLog
 SY_System . . . . . . . . . . . . . . . System Preferences
 SY_SystemConfigListingWrk . . . . . . . SY System Configuration Listing Work
 SY_Task . . . . . . . . . . . . . . . . SY Task Master
 SY_TaskSchedulerDetail. . . . . . . . . SY Task Scheduler Detail
 SY_TaskSchedulerHeader. . . . . . . . . SY Task Scheduler Header
 SY_TaskSchedulerListingWrk. . . . . . . SY Task Scheduler Listing Work
 SY_TaskType . . . . . . . . . . . . . . SY Task Type Master
 SY_Template . . . . . . . . . . . . . . SY Template
 SY_TemplateSetting. . . . . . . . . . . SY Office Template Setting
 SY_Terminal . . . . . . . . . . . . . . SY Terminal
 SY_Theme. . . . . . . . . . . . . . . . User Interface Theme
 SY_Token. . . . . . . . . . . . . . . . SY Token
 SY_URLMaintenance . . . . . . . . . . . URL Maintenance
 SY_User . . . . . . . . . . . . . . . . SY User Master
 SY_UserAutoComplete . . . . . . . . . . SY User Auto-Complete
 SY_UserHistory. . . . . . . . . . . . . SY User History
 SY_UserRegistry . . . . . . . . . . . . SY User Registry
 SY_UserReportWrk. . . . . . . . . . . . SY User Report Work
 SY_UserSecurity . . . . . . . . . . . . SY User Security
 SY_UserSettingsListingWrk . . . . . . . SY User Settings Listing Work
 SY_UserTableSecurity. . . . . . . . . . SY User Table Security
 SY_UserTableSecurityReportWrk . . . . . SY User Table Security Report Work
 SY_WizardListingWrk . . . . . . . . . . SY Wizard Listing Work
 SY_Workstation. . . . . . . . . . . . . SY Console
 SY_ZipCode. . . . . . . . . . . . . . . SY Zip Code Master
 SY_ZipCodeEdit. . . . . . . . . . . . . SY Zip Code Edit
 SY_ZipCodeListingWrk. . . . . . . . . . SY Zip Code Listing Work

------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

Original Message:
Sent: 02-05-2019 16:08
From: Mary Mays
Subject: Installed modules list

Thanks.  I have installed a clean Sage and migrated from a version with the links folder cleaned out to hopefully get rid of the modification.  Doesn't seem to be anywhere in the new install EXCEPT in the installed modules listing.

 

Mary Mays Professional Software, Inc.  DSD Wichita, Inc. 800 East First Street, Suite 150 Wichita, KS  67202 phone: (316)269-4264   fax: (316)269-0512

         

 

 

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify mmays@pskansas.com immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

 

Original Message------

short answer: I don't know where the listing gets its info.
long answer: Removing mods from the listing but not the product, they may come back to bite you, yet. Even if you didn't re-install them after upgrading.  But that said, I know there is info in the Links folder and I've renamed it to resolve certain issues.

Here's something on that topic. 

Sage 100 (formerly Sage MAS 90 or 200) versions 4.00 through 4.50; and 2013 and higher:

1. Open Modules, Library Master, Reports menu, Installed Modules Listing
2. Check the modules listed for non-standard MAS 90 or 200 programs, asterisks by the modules, or level numbers that are not consistent with the existing level number.

MAS 90 or 200 versions 3.71 and earlier:

1. Open Modules, Library Master, Utilities menu, Installed Applications Listing
2. Check the applications listed for non-standard MAS 90 or 200 programs, asterisks by the modules, or level numbers that are not consistent with the existing level number.

To check whether a third-party module may be activated for specific companies:

1. Open Library Master, Main menu, Company Maintenance
2. For Company Code, select a company
3. In the Activated Modules area, check for any non-standard application modules.

Program files added by third-parties:

• The "..\MAS90\Links" folder (on the server where Sage 100 is installed) may contain third-party program files other than Default.pvc. Any program file in that directory other than Default.pvc indicates existence of third-party program enhancement(s).
  • Note: Not all third-party developers follow this rule. A Sage 100 system with only Default.pvc in the "..\MAS90\Links" folder may still be modified, with third-party developers directly replacing standard Sage 100 program files in other folders/directories. In other words:
    • If the problem no longer occurs after files in the "Links" folder are temporarily removed, then that would prove the issue is due to third-party modification.
    • However, if the problem still occurs after files in the "Links" folder are temporarily removed, that does not prove the issue is not due to third-party modification.
  • Note: Third-party enhancements for Legacy (non-Business Framework) application modules typically do not use the "Links" folder.
• Standard Sage 100 Business Framework program files typically do not have numbers in their file names. Sometimes third-party developers use numbers in program file names: It could be their developer code, or it could be a catalog or product number (for their software product), etc.
  • If an error message occurs with a program file that is not a standard Sage 100 program file, then it is likely a third-party program issue.
  • The SY_Developer.m4t data file contains a list of records, each with a 3-digit DeveloperCode key, and a second field, DeveloperName. If you have a program with a number in it, that may correspond to the code of the developer.

------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

------Original Message------

Let's see, the reports comes from a work file.  The workfile is probably made from these tables.  Sy_Module?

SY_Activation . . . . . . . . . . . . . SY Activation
 SY_ActivationReq. . . . . . . . . . . . SY Activation Requirements
 SY_ActivityLog. . . . . . . . . . . . . SY Activity Log
 SY_ActivityLogReportWrk . . . . . . . . SY Activity Log Report Work
 SY_ActivityType . . . . . . . . . . . . SY Activity Type
 SY_BaseODBCSecurity . . . . . . . . . . SY Base ODBC Security
 SY_BatchManager . . . . . . . . . . . . SY Batch Manager
 SY_Broadcast. . . . . . . . . . . . . . SY Broadcast
 SY_ClassEnhancement . . . . . . . . . . SY Class Enhancement
 SY_Company. . . . . . . . . . . . . . . SY Company Master
 SY_CompanyListingWrk. . . . . . . . . . SY Company Listing Work
 SY_Console. . . . . . . . . . . . . . . SY Console
 SY_Context. . . . . . . . . . . . . . . SY Context
 SY_ContextAFM . . . . . . . . . . . . . SY Context Advanced Field Mappings
 SY_ConversionDriver . . . . . . . . . . Conversion Driving Records
 SY_ConversionHistory. . . . . . . . . . System Conversion History
 SY_Country. . . . . . . . . . . . . . . SY Country Master
 SY_CreditCardProcessXref. . . . . . . . SY Credit Card Process Xref
 SY_CreditCardRestart. . . . . . . . . . SY Credit Card Restart
 SY_CrystalAnalysisWrk . . . . . . . . . SY Crystal Analysis Work
 SY_Deferred . . . . . . . . . . . . . . Deferred Printing Master
 SY_Developer. . . . . . . . . . . . . . SY Develope
 SY_DeveloperManifest. . . . . . . . . . Developer Manifest
 SY_Dialog . . . . . . . . . . . . . . . SY Dialog
 SY_DialogSettings . . . . . . . . . . . SY Dialog Settings
 SY_DictionaryConversionHist . . . . . . Dictionary Conversion History
 SY_EBusinessManagerUserID . . . . . . . SY EBusiness Manager User ID
 SY_EISViewMaster. . . . . . . . . . . . SY EIS View Master
 SY_EmbeddedIOSettings . . . . . . . . . SY EmbeddedIOSettings
 SY_Enhancement. . . . . . . . . . . . . SY Enhancement
 SY_EnhancementModule. . . . . . . . . . Enhancement Level Info
 SY_ExportLink . . . . . . . . . . . . . Export Link
 SY_ExtendedSolutionUDFConvWork. . . . . SY Extended Solution UDF Conversion Work
 SY_FieldMapping . . . . . . . . . . . . SY Field Mapping
 SY_FinancialReport. . . . . . . . . . . GL  FinancialReport
 SY_FinancialReportColumn. . . . . . . . Financial Report Column Mapping
 SY_FinancialTerminology . . . . . . . . Default Financial Terminology Descriptions
 SY_FormsEFilingVersion. . . . . . . . . Forms eFiling Version
 SY_GridDefinition . . . . . . . . . . . Grid definition
 SY_InstalledModulesListingWrk . . . . . SY Installed Modules Listing Work
 SY_JournalErrorLogWrk . . . . . . . . . SY Journal Error Log Work
 SY_LastFormUsed . . . . . . . . . . . . SY Last Form Used
 SY_LinkPathsWork. . . . . . . . . . . . SY _Link Paths Work
 SY_LockFiles. . . . . . . . . . . . . . SY Lock Files Reference
 SY_MemoDefault. . . . . . . . . . . . . SY Memo Default
 SY_MemoManager. . . . . . . . . . . . . SY Memo Manager
 SY_MemoRelationship . . . . . . . . . . SY Memo Relationship
 SY_MemoSettingsListingWrk . . . . . . . SY Memo Settings Listing Work
 SY_Menu . . . . . . . . . . . . . . . . SY Menu
 SY_Message. . . . . . . . . . . . . . . Messages
 SY_Metering . . . . . . . . . . . . . . Metering
 SY_Module . . . . . . . . . . . . . . . SY Module
 SY_ModuleDate . . . . . . . . . . . . . Module Access Date
 SY_ModuleDateListingWrk . . . . . . . . SY Module Date Listing Work
 SY_MultiPartForm. . . . . . . . . . . . SY Multi Part Form
 SY_NoMessage. . . . . . . . . . . . . . SY No Message
 SY_ODBCSecurity . . . . . . . . . . . . SY ODBC Security
 SY_PaymentCenterReference . . . . . . . Payment Center Access Reference
 SY_PayrollEFilingMapping. . . . . . . . Payroll EFiling Mapping (PIM)
 SY_PeriodEndListingWrk. . . . . . . . . SY Period End Listing Work
 SY_PeriodEndReport. . . . . . . . . . . Period End Report
 SY_Personalize. . . . . . . . . . . . . SY Personalize
 SY_PersonalizeALE . . . . . . . . . . . SY Personalize ALE
 SY_PollingSystem. . . . . . . . . . . . SY Polling System
 SY_PopupItem. . . . . . . . . . . . . . Popmenu Item
 SY_PopupMenu. . . . . . . . . . . . . . Popup menu Menus
 SY_PopupMenuItem. . . . . . . . . . . . Popup menu item
 SY_PopupXref. . . . . . . . . . . . . . Popupmenu panel Xref
 SY_PreMigrationCompany. . . . . . . . . SY Pre Migration Company
 SY_PreMigrationItemCode . . . . . . . . SY Pre Migration Item Code
 SY_PreMigrationWarehouse. . . . . . . . SY Pre Migration Warehouse
 SY_PrinterPreferences . . . . . . . . . SY Printer Preferences
 SY_ProcessFlows . . . . . . . . . . . . Process Flows
 SY_RebuildLog . . . . . . . . . . . . . SY Rebuild Log
 SY_Relation . . . . . . . . . . . . . . SY Relation
 SY_ReportManagerFormat. . . . . . . . . SY Report Manager Format
 SY_ReportManagerMaster. . . . . . . . . SY Report Manager Master
 SY_ReportManagerTemplate. . . . . . . . SY Report Manager Template
 SY_ReportOption . . . . . . . . . . . . Report Option
 SY_ReportSelection. . . . . . . . . . . Report Selection
 SY_ReportSetting. . . . . . . . . . . . SY Report Setting
 SY_ReportSettingsListingWrk . . . . . . SY Report Settings Listing Work
 SY_ReportWizardExpressions. . . . . . . SY Report Wizard Expressions
 SY_ReportWizardFields . . . . . . . . . SY Report Wizard Fields Used
 SY_ReportWizardFilters. . . . . . . . . SY Report Wizard Filters
 SY_ReportWizardGroups . . . . . . . . . SY Report Wizard Groups
 SY_ReportWizardLinks. . . . . . . . . . SY Report Wizard Links
 SY_ReportWizardMain . . . . . . . . . . Report Wizard main file
 SY_ReportWizardRoles. . . . . . . . . . SY Report Wizard Roles
 SY_ReportWizardSorts. . . . . . . . . . SY Report Wizard Sorts
 SY_ReportWizardSources. . . . . . . . . SY Report Wizard Sources
 SY_ResourceRoleSecurity . . . . . . . . SY Resource Role Security
 SY_Role . . . . . . . . . . . . . . . . SY Role Master
 SY_RoleReportODBCSecurityWrk. . . . . . SY Role Report ODBC Security Work
 SY_RoleReportWrk. . . . . . . . . . . . SY Role Report Work
 SY_RoleSecurity . . . . . . . . . . . . SY Role Security
 SY_SagePEP. . . . . . . . . . . . . . . Sage Product Enhancement Program - key/value pairs
 SY_SagePEPSettings. . . . . . . . . . . Sage Product Enhancement Program - Settings
 SY_SagePEPTask. . . . . . . . . . . . . Sage Product Enhancement Program - Track Tasks
 SY_SagePEPTrack . . . . . . . . . . . . Sage Product Enhancement Program - Track Data/Events
 SY_SalesTaxClass. . . . . . . . . . . . SY Sales Tax Class
 SY_SalesTaxCode . . . . . . . . . . . . SY Sales Tax Code
 SY_SalesTaxCodeDetail . . . . . . . . . SY Sales Tax Code Detail
 SY_SalesTaxCodeListingWrk . . . . . . . SY Sales Tax Code Listing Work
 SY_SalesTaxSchedule . . . . . . . . . . SY Sales Tax Schedule
 SY_SalesTaxScheduleDetail . . . . . . . SY Sales Tax Schedule Detail
 SY_SalesTaxScheduleListingWrk . . . . . SY Sales Tax Schedule Listing Work
 SY_SalesTaxScheduleStateXRef. . . . . . SY Sales Tax Schedule State XRef
 SY_SalesTaxScheduleZipXRef. . . . . . . SY Sales Tax Schedule Zip XRef
 SY_SampleAccounts . . . . . . . . . . . SY SampleAccounts
 SY_SampleAccountsWrk. . . . . . . . . . SY Sample Accounts Work
 SY_SQLOptimize. . . . . . . . . . . . . SY SQL Optimize
 SY_StarShipWork . . . . . . . . . . . . StarShip Work File
 SY_State. . . . . . . . . . . . . . . . SY State Code Master
 SY_Surrogate. . . . . . . . . . . . . . SY Surrogate
 SY_SurrogateLog . . . . . . . . . . . . SY_SurrogateLog
 SY_System . . . . . . . . . . . . . . . System Preferences
 SY_SystemConfigListingWrk . . . . . . . SY System Configuration Listing Work
 SY_Task . . . . . . . . . . . . . . . . SY Task Master
 SY_TaskSchedulerDetail. . . . . . . . . SY Task Scheduler Detail
 SY_TaskSchedulerHeader. . . . . . . . . SY Task Scheduler Header
 SY_TaskSchedulerListingWrk. . . . . . . SY Task Scheduler Listing Work
 SY_TaskType . . . . . . . . . . . . . . SY Task Type Master
 SY_Template . . . . . . . . . . . . . . SY Template
 SY_TemplateSetting. . . . . . . . . . . SY Office Template Setting
 SY_Terminal . . . . . . . . . . . . . . SY Terminal
 SY_Theme. . . . . . . . . . . . . . . . User Interface Theme
 SY_Token. . . . . . . . . . . . . . . . SY Token
 SY_URLMaintenance . . . . . . . . . . . URL Maintenance
 SY_User . . . . . . . . . . . . . . . . SY User Master
 SY_UserAutoComplete . . . . . . . . . . SY User Auto-Complete
 SY_UserHistory. . . . . . . . . . . . . SY User History
 SY_UserRegistry . . . . . . . . . . . . SY User Registry
 SY_UserReportWrk. . . . . . . . . . . . SY User Report Work
 SY_UserSecurity . . . . . . . . . . . . SY User Security
 SY_UserSettingsListingWrk . . . . . . . SY User Settings Listing Work
 SY_UserTableSecurity. . . . . . . . . . SY User Table Security
 SY_UserTableSecurityReportWrk . . . . . SY User Table Security Report Work
 SY_WizardListingWrk . . . . . . . . . . SY Wizard Listing Work
 SY_Workstation. . . . . . . . . . . . . SY Console
 SY_ZipCode. . . . . . . . . . . . . . . SY Zip Code Master
 SY_ZipCodeEdit. . . . . . . . . . . . . SY Zip Code Edit
 SY_ZipCodeListingWrk. . . . . . . . . . SY Zip Code Listing Work

------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

sy0ctl.soa ?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 02-05-2019 16:08
From: Mary Mays
Subject: Installed modules list

Thanks.  I have installed a clean Sage and migrated from a version with the links folder cleaned out to hopefully get rid of the modification.  Doesn't seem to be anywhere in the new install EXCEPT in the installed modules listing.

 

Mary Mays Professional Software, Inc.  DSD Wichita, Inc. 800 East First Street, Suite 150 Wichita, KS  67202 phone: (316)269-4264   fax: (316)269-0512

         

 

 

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify mmays@pskansas.com immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

 

Original Message------

short answer: I don't know where the listing gets its info.
long answer: Removing mods from the listing but not the product, they may come back to bite you, yet. Even if you didn't re-install them after upgrading.  But that said, I know there is info in the Links folder and I've renamed it to resolve certain issues.

Here's something on that topic. 

Sage 100 (formerly Sage MAS 90 or 200) versions 4.00 through 4.50; and 2013 and higher:

1. Open Modules, Library Master, Reports menu, Installed Modules Listing
2. Check the modules listed for non-standard MAS 90 or 200 programs, asterisks by the modules, or level numbers that are not consistent with the existing level number.

MAS 90 or 200 versions 3.71 and earlier:

1. Open Modules, Library Master, Utilities menu, Installed Applications Listing
2. Check the applications listed for non-standard MAS 90 or 200 programs, asterisks by the modules, or level numbers that are not consistent with the existing level number.

To check whether a third-party module may be activated for specific companies:

1. Open Library Master, Main menu, Company Maintenance
2. For Company Code, select a company
3. In the Activated Modules area, check for any non-standard application modules.

Program files added by third-parties:

• The "..\MAS90\Links" folder (on the server where Sage 100 is installed) may contain third-party program files other than Default.pvc. Any program file in that directory other than Default.pvc indicates existence of third-party program enhancement(s).
  • Note: Not all third-party developers follow this rule. A Sage 100 system with only Default.pvc in the "..\MAS90\Links" folder may still be modified, with third-party developers directly replacing standard Sage 100 program files in other folders/directories. In other words:
    • If the problem no longer occurs after files in the "Links" folder are temporarily removed, then that would prove the issue is due to third-party modification.
    • However, if the problem still occurs after files in the "Links" folder are temporarily removed, that does not prove the issue is not due to third-party modification.
  • Note: Third-party enhancements for Legacy (non-Business Framework) application modules typically do not use the "Links" folder.
• Standard Sage 100 Business Framework program files typically do not have numbers in their file names. Sometimes third-party developers use numbers in program file names: It could be their developer code, or it could be a catalog or product number (for their software product), etc.
  • If an error message occurs with a program file that is not a standard Sage 100 program file, then it is likely a third-party program issue.
  • The SY_Developer.m4t data file contains a list of records, each with a 3-digit DeveloperCode key, and a second field, DeveloperName. If you have a program with a number in it, that may correspond to the code of the developer.

------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

Short Answer: I know where the Listing gets it info from but in my view, all the warnings Rhonda pointed out almost always supersede the need to print a clean Listing. It can just totally come back to bite you in the butt.

Removing the appropriate records for the mods in question from the main Sy_Enhancement table will hide it from the listing but does not at all mean you have cleanly removed the mod (and leaving it there doesn't mean the mod is in use either). There are several more places most of which not mentioned in this Sage KB article to cleanly uninstall and caveats to deal with.  Developer create their own custom folders and files as well. What it mentions about generally disabling a (Framework) mod via \Links folder is correct.

*** If you're willing to risk hiding the mods from the Listing, do it by modifying the Crystal RPT file to say DeveloperCode = "000" instead of DFDM deleting a bunch of records from a bunch of files.

Now once I did remove the eBusiness Manager module (the 3 rows for .Order, .Inquiry, .Store) because after telling the Sage sales rep the client doesn't use it anymore and not to include for the next renewal she needed proof it was uninstalled. Of course you can't uninstall eBM and instead of trying to convince her I did next best thing :-) 

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------

------Original Message------

Short Answer: I know where the Listing gets it info from but in my view, all the warnings Rhonda pointed out almost always supersede the need to print a clean Listing. It can just totally come back to bite you in the butt.

Removing the appropriate records for the mods in question from the main Sy_Enhancement table will hide it from the listing but does not at all mean you have cleanly removed the mod (and leaving it there doesn't mean the mod is in use either). There are several more places most of which not mentioned in this Sage KB article to cleanly uninstall and caveats to deal with.  Developer create their own custom folders and files as well. What it mentions about generally disabling a (Framework) mod via \Links folder is correct.

If you're willing to risk hiding the mods from the Listing, do it by modifying the Crystal RPT file to say DeveloperCode = "000" instead of DFDM deleting a bunch of records from a bunch of files.

Now once I did remove the eBusiness Manager module (the 3 rows for .Order, .Inquiry, .Store) because after telling the Sage sales rep the client doesn't use it anymore and not to include for the next renewal she needed proof it was uninstalled. Of course you can't uninstall eBM and instead of trying to convince her I did next best thing :-) 

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------