Custom programming has evolved to the database level. SQL scripts may be used to created new data tables and write data to those tables (e.g., create a table to receive the tracking number from your shipping system). They can also be used to create views to simplify reporting.
My favorite example of a SQL script is Material Overhead Update. The process is simple; enter a new overhead rate, write that rate to the Part Master for all purchased parts, and then recalculate the total cost for the part using material, labor, overhead and subcontract cost elements. Twenty-five years ago we wrote this as Visual Basic application. Today, it is a script that resides in your database. There are obvious savings in overhead between the two approaches.
Convert Configured Order is the most complex example of how SQL processing can be exploited. This script will read the configuration string for a Features and Options Sales Order and convert that data into a new, unique Part Identifier and standard Bill of Material (BOM). This allows the completed configured part to be stocked (i.e., finished goods and consignment at dealers/distributors) and managed as "normal" inventory. Having "normal" engineering documentation also facilitates servicing that product going forward.
To learn how to run these scripts from a desktop shortcut, your MAX Control Panel or MAX Tool Menu, and to add password controlled security for the execution of these scripts, see our Process Executor offer.
Need a SQL Procedure or View?
Choose from our library of 65+ existing reports. See the "Downloads" section below. If you cannot find what you are looking for, use the "Contact Me" link below for help.
Utilize Microsoft's SQL Server to automate processes and reporting in your MAX database with our SQL
See our 'Process Executor' page for script execution from the desktop, System Manager Control Panel or Tool Menu.