Accounts Payable Survey

04/09/18 Prestige, Inc. Procedure’s Script ID: QUOTE TESTING.

Written By: Tom Herrmann Date: 06/30/04 Revised: 4/12/05

To be Trained: ______

GETTING TO THE TEST PROGRAM

1. Click Help About 2. Click on the Prestige logo in the About window. 3. Close the About window. 4. Click the unlabled check box to the right of Job Number of the screen of the main menu.

5. The Debug button should appear when you check this box.

Clicon on the Debug button. The following screen will appear.

6. Click on Test button to get to the test screen.

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 1 of 18 04/09/18 Prestige, Inc. Procedure’s TEST

AUTOMATED TESTING BY STYLES

Test Screen has the following parameters:

OE53 Parameters: ShipTo – the ship to customer number OrderDate – the order date (the PRICECODE segment is controlled by the order date)

Testing Parameters: Price Increase – percentage to add to the electronic price book to get the validation price Allowed Error – the allowed difference between CompPrice and TestPrice to pass the test Write PriceBookNew – when checked writes results to PriceBookNew table, tests are only ran on one cabinet per price book entry. No non-standard bread board cabinets will be tested either. Write RPData – when selected and the test passes the door prices for the cabinet are saved in RPDOORPrice# (where # is the PriceCode).

Test Selection Method: Models w/NotReq unchecked – models are tested that have the NotReq field unchecked for the style being tested. The not required data can either be the not required price column or the not required style. Models w/NotReq unchecked beginning with – the same selection method using the not required field except only the models beginning with the value entered into the box are tested. Example, if BD is entered into the box then only base drawers are tested that have their not required unchecked. Run Test Snapshot – If Select Runs is checked and this is checked the tests that were selected when Snapshot Tests button was clicked will be ran. Test Only Asterisk Prices in PricebookNew also includes any PBCodes not in PricebookNew – this will test codes with an asterisk in the price column for a model. Also any codes that should appear in PricebookNew that are blank will be tested. Model with Failed checked in Test Tracking – the test tracking results are used to select models to test. The model must have been ran previously and failed to be selected. Test Pricebook Only – this will test only those cabinets that have a PBCode in VCabData that appears in

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 2 of 18 04/09/18 Prestige, Inc. Procedure’s the Blocks table and do not have Not In Pricebook checked. If the PBCode is not in Blocks table then it is assumed it is not in the pricebook. Test Not in Pricebook Only – this will test only those cabinets that are NOT in the pricebook. All models that are required for the style being tested and do not have a PBCode in the blocks table. If they do have a PBCode in the Blocks table the Not In Pricebook must be checked to be included in this test set. When both the Test Pricebook Only and the Test Not In Pricebook Only are both not checked all codes are tested. Test NotInPDQ unchecked (PDQ only models) – this will select any models that have NotInPDQ unchecked in the Blocks table and have Not Required unchecked.

Test Selection: Save Segment Results – When checked the segments are saved for each cabinet tested. Unchecking will not save the segment results. Not saving the segment results will make testing go faster. Select Runs – when checked Test “Styles To Test” button will select the tests according to the Styles To Test and Test Pricebook Only. If not checked then the current tests selected will be ran. This feature allows you to select individual cabinets for testing. Unchecking Select Runs will stop any selecting of tests for the first style to test. On the second style to test Select Runs will be checked and the styles to select will be done based on Failed Only and RunTest Snapshot.

Clear All Tests: This button will clear all the cabinet codes for testing.

Mark Failed Tests: This button will take all the cabinet codes in the test results that have failed and mark them for running again.

Snapshot Tests: This button will save all the cabinets that are selected to test for testing. When the Run Test Snapshot is checked then these cabinets are are selected are recalled for testing when tests are ran.

RUNNING ALL TESTS FOR A STYLE 1. Go to GL page and select all the styles to test 2. Choose the selection method for models to test. 3. Click First Run Select 4. Click on Run Styles To Test

Steps performed when Run Styles To Test is executed:

1. The 1st Style To Test is set in the GL options along with the ED. 2. The nrPrcCol field is used to determine what cabinet codes are to be tested. If the nrPrcCol is blank then the nrStyle is used and cabinets are tested according to the specific style. These are setup under the NotReq tab for Price columns and Styles. 3. The GL model is executed and the results feed to the first model for test. 4. The model is tested and the TestPrice is obtained. 5. The ElecPrice is retrieved by using the PriceColumn that is setup n the PriceCol table. 6. The BB option is also checked and if needed price is looked up. 7. If the TestPrice and the ElecPrice plus options and price increase are within the Allowed Error then the cabinet passes.

The compare price is obtained by looking into table PriceBook# (where # is the PRICECODE). The column to use is determined by table StylePriceColumn#. The Style and 5 piece option are used to lookup the price column. If there is a multiplier on the the price column then PriceAdj

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 3 of 18 04/09/18 Prestige, Inc. Procedure’s RESULTS

Click the Results table to view the test results page. Update Results – click to view all newly ran tests. This will also set the flags for the tracking summary for tests passed and tested.

Clear Results – This button will erase all test results. Segment Values – This button can be used to view the segment results of a test. Select the cabinet to view the segments then click “Segment Values”. Tracking Summary – Displays Tracking Summary report. To clear the results to start over go to the GL page and click Clear Passed Tests for Selected Styles. To check to see what cabinets were untested go the Untested page and pull down the price column to check. Also if PriceBook only is checked then all those cabinets will appear in the untested count. Style (Tracking Summary) – Displays the tracking summary report for just style/5piece tests. Email – this button will send the failed results to the email addresses listed in email group FAILED. See BUILD section for information on setting up email recipients. Print Failed – prints a copy of the failed results, same information that is emailed.

The result columns are as follows:

Pass - when checked the TestPrice is within the allowed error of the CompPrice. TestNum – test number CabCode – product used to test TestPrice – result of AS400 model test ElecPrice – price found in PriceBook# CompPrice – ElecPrice plus any options like BB plus any price increase W,c,f,bb,dv – option list Option Prices – this will list the price added to the TestPrice per option PBCode – price book code used to lookup ElecPrice in PriceBook# Block – block CabCode is found in price book, if an asterisk is after the block the Not In Pricebook is checked ErrMsg – error messages generated during the test. This could be edit messages from the PCM and program generated messages. These are intended to help trouble shoot failed models.

ERROR MESSAGES NotReq PriceCol doesn't match! – The test was trying to test a cabinet that had used the not required from a different not required for the style/5 pc. This happens when the style was forced to change. For example, testing a B09L for Cathedral (not req Style is C) the style is forced to P (not req is PF) . This causes a mismatch so an error is generated. Price Book Column not found for Style: ## 5PC: #! – The price book column for the style and 5 piece options are not in the table PriceCol. Goto PriceCol page and check for style and 5 piece option to have a Price Column. Pricebook code ##### missing in PriceBook# table! – The PBCode is not in the PriceBook# table. Verify the price book code is correct for the cabinet being tested. BreadBoardCodes table is missing entry for breadboard code, BB## - The BB code is not setup for the cabinet being tested. Goto tab Options and check cabinet code entry in the Bread Board Codes table. PCM EDIT MESSAGES – Edit messages generated by the PCM code.

TRACKING REPORTS FOR STYLES

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 4 of 18 04/09/18 Prestige, Inc. Procedure’s The Tracking Summary button contains the list of anchor styles for the different price columns. These are the Not Req By Price Column styles.

This price tracking report is displayed with the Style button beside the Tracking Summary button. These are the styles from the Not Req By Style.

Price Column-Style/5pc/*FO – this column contains the price column for the style tested. The price column is pulled from the PriceCol table. If there is no price column as in “.-AA” above it means there is no price column assigned for the style AA in the PriceCol table. Also the Not Req Style’s have a Pass/Tested field that contains the pass/fail/untested info. In order to add a style to this report there must be a Not Req Style. Pass – the number of cabinet codes that pass with the percentage of the required cabinets to test. Fail – the number of cabinet codes that fail with the percentage of the required cabinets to test. Untested - – the number of cabinet codes that have not had tests ran, with the percentage of the required cabinets to test. Some of these may be there because the style is forced to a different style than the one tested. For example style C sometimes forces to style P. These cabinets would need to be selected as not required.

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 5 of 18 04/09/18 Prestige, Inc. Procedure’s Req – number of cabinet codes to test Not Req – number of cabinets marked as not required for style Total – total cabinets in system

PRICE TESTING TRACKING REPORT FOR PRICE COLUMN This is the report that is displayed when Tracking Summary

ELECTRONIC PRICEBOOKS

Tables PriceBook1, PriceBook2 and PriceBook3 are the prices to validate against for the three different price codes. Normal testing will have the values the prices should be in the appropriate price code and the Price Inc should be 0. However, during the time of generating a new price book the new price code PriceBook will not have that pricebooks prices.

For example, when going from price code 3 to 1 the PriceBook3 table will be copied to PriceBook1 table. At that time PriceBook1 will actually have PriceBook3 prices. This is when you use the Price Inc. Validation will use the PriceBook1 table price plus the Price Inc amount to validate the prices. PriceBook1 should be modified to reflect Price Code 3 prices during this period. Sometimes cabinet prices were wrong in price code 3 are are going to be updated with price code 1. The price code 3 prices should be placed in the PriceBook1 table for validation and new pricebook building. During the building of the pricebook PriceBookNew table will be populated with the new prices that pass validation. Once the prices are all build and the PriceBookNew table is completed and the generation process is completed, PriceBookNew should be copied to PriceBook1 and the Price Inc should be removed. This will complete the cycle for going from Price Code 3 to 1.

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 6 of 18 04/09/18 Prestige, Inc. Procedure’s GL

GL TABLE The table of Segment and Value are the values that the GL model is initialized when running a test.

STYLE TO TEST This is a table of all available styles. The Test column is checked that style will be tested when the “Test Styles Model” button is clicked on the Test page. When a test is ran the GL options are set according to this table. The following GL segments get set from the Styles to Test table:

SDB - Style SDW - Style DRW5PC - DRW5PC ED - ED C.ED - ED

The Styles To Test table also sets values in the Test Section of the Test page. The Not Req Prc Col is set to “nrPcrCol”. If nrPrcCol is blank then the nrStyle is set to Not Req Style along with the 5PC. These columns are how you choose the proper not required definitions. One of the problem with this is for styles that force a different style, for example Cathedral forces Square on 9” base cabinets. If you are testing a 9” base cabinet with cathedral style then the test will fail because the result of the test is expecting the style to remain C. This would indicate that the not required for style C would need to be selected because it is not necessary to test a cathedral cabinet for 9” bases. When you test Square the price will be verified. The forced style change must be tested manually.

Clear Passed Tests For Selected Styles – The style checked for Test will have the Pass and Tested flags cleared to restart testing for that price column. Reset All Test Tracking – This will clear all Pass Tested flags in all price columns and styles.

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 7 of 18 04/09/18 Prestige, Inc. Procedure’s OPTIONS

The left table contains the cabinet code, option and option value to assign during testing. This table is to satisfy the mandatory options that are not from the globals. The first example shows the B12CL will set the BB option to 1 when tested. This can be done for any option and any multiple of options. For example the FPB can have two options set.

Bread board options add an option upcharge to the TestPrice. The table Bread Board Assign is used to determine what BB code to lookup in PriceBook# when determining the CompPrice. The above example shows BB12 will be priced for B12CL.

The Pass Num can be used to run multiple passes on the same CabCode but with different options.

Entering a Model will display all the option values that will be set when that model is tested. One of the problems with testing the 6000 block cabinet codes is finding the price column of the electronic price. This can be done by

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 8 of 18 04/09/18 Prestige, Inc. Procedure’s entering “.PC” into the Option column and then entering PA, PB, PC…. into the Value field (NoStyle will also work). The PassNum will connect a group of segment values to run during a pass. The above example shows how all four price columns for cabinet code FPS will be tested. If the “.PC” is missing from the options then the style column for the electronic pricebook is determined from the Style/Drw5pc just as when there are no options values set.

Once a cabinet has a pass number entry the only tests that will be performed is defined by the pass numbers. For example, the SH##F products need no options set for package quantity but do for package quantity of five. There has to be a pass added with .PC equal to ‘NoStyle’ in order for a test to be ran.

CHANGING OPTIONS BASED ON STYLE

The SRC cabinets need to have the C.ED option changed for style DF. If you set the C.ED option for all styles then some styles will fail. Two entries are requred to set this up. An entry in the Options for Models need to be made for each pass needed. Secondly the Options By Style table must be filled in with the cabcode, option, value, style, 5 piece option and the pass number. The style will be the style chosen when the test starts. For example, SRC36 will not have a 5 pieice but the style starts with the 5 piece set to ‘Y’.

Add XLS Options – this button will import from the C:\_PCMCompiler\Quote.xls spread sheet. Below is an example of the spreadsheet format. Note, all numbers must be preceeded by a single quote to make them a text string when importing.

.CabCode .Segment .Value .PassNum F612 .PC PK 1 F615 .PC PK 1 F618 .PC PK 1 F621 .PC PK 1

PRICEBOOK

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 9 of 18 04/09/18 Prestige, Inc. Procedure’s This is a viewer into the PriceBook# tables. Enter 1,2,3 or New into PriceCode to view these different tables. VcabData cross references the cabinet code to the price book code to be able to lookup a price. PRICE COL

This price column table determines the price column in PriceBook# based on the style and the 5 piece option. The PriceCode connects the PriceBook# and the PriceCol# tables. For example, to setup a style AA to price in price column G for price code 3 you would do the following.

1. Enter 3 in the PriceCode box. 2. Go to the end of the table where the asterisk appears and enter AA in the Style column. 3. Leave DRW5PC blank 4. Enter PG in the PriceColumn 5. Enter 1 in the PriceAdj

Also a price adjustment can be added to the price column so you can build a new style based off an existing style price.

When the cabinet is finished getting the TestPrice the S and DRW5PC segments are looked up in this table. This will return a price column. This price column is used to lookup the price for PBCode in the appropriate PriceBook# table. The Price Adj value can be entered for the style to upcharge only a price column. For example when we introduced Nottingham PriceAdj was 1.05 and PriceColumn was PA. This caused the ElecPrice to be PA column times 1.05. NOT REQ

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 10 of 18 04/09/18 Prestige, Inc. Procedure’s

The Not Required By Price Column section determines if a cabinet can be tested in that price column. When the “Test Style Model” button is clicked on the Test page. The Styles To Test table, field nrPrcCol, is used determine which not required price column to use and not select those cabinets for testing. Since there are multiple styles in one column and some styles do not have some cabinets that others will the Not Required By Style table was created. For example Cathedral cannot be on 9” cabinets but is in price column PF with Square. Pull down the C a Not Req check box can be selected for all 9” cabinets. The pull down window displays all the styles that are setup along with the 5 piece option. The 5 piece option must be entered manually into the field just to the right of the pull down. A period is used for the 5 piece options when the style is not 5 piece. Five piece is Y when style has 5 piece.

Style XX Only (button on left) – this will set all the not required fields except NoStyle for the cabinet selected in the left window. Style XX Only (button on right) – this will set all the not required fields except NoStyle for the cabinet selected in the right window. Copy Style – this will copy the style being displayed in the Not Req By Style section to a different style. For example you could use this button to make a copy of JC with no 5 piece to JC with 5 piece. The 5 piece option is located to the right of the style. If the 5 piece is no then enter a period ‘.’ into the 5 piece option. Delete Style – this will delete all the not required cabinet codes for the style that is in the pull down window. You must also enter the 5 piece option. UNTESTED

This page allows you to examine the cabinet codes for a price column that are untested. These are cabinets that do not have tested checked and are required (not require isn’t checked). This can be done after a price column is completely tested. Use the pull down window to select the price column. You can click the not required on this screen if you find the cabinet is not required. You can also use “Selected Cabinet set for Style XX” button to set all not required for all price columns and styles, except NoStyle.

BLOCKS

The Blocks table is where the blocks that get into the price book are defined.

PBCode - Price book code Block - Block to place price book code Dash - order to place PBCode in price book, if left blank then they will be in alphabetic order by PBCode Hinge - Left/right and footnote references for price book Not In Pricebook - code is not in price book but if it was would fall in this block

This is the actual table that builds the price book. Be sure to check Not In Pricebook if the cabinet is not to be in the pricebook.

The data can be sorted by PBCode if the PBCode column title is clicked. Also can be sorted by Block. VCABDATA

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 12 of 18 04/09/18 Prestige, Inc. Procedure’s This table links the Cabinet Code with the Price Book code. CabCode should be exactly as the cabinet is typed into OE53. PBCode is what appears in the PriceBook# tables.

ADDING NEW MODELS

Occationally models with options lists for the models are added to the PCM library. The following describes how to add these models to the program. The models are added to VcabData and the proper Not Req tables. Goto the VcabData tab. 1. The new models will be extracted from the PIP-Local table located in the GetPCMLibrary97.mdb database. 2. Click on “Add New Models From Library” – this will access the PIP-Local table in GetPCMLibrary97 and include all new CabCode’s that are not in VCabDataModels table. Products that have the Generic “DELETE” will not be added to VCabData. 3. Click on “Remove Models from VCabdata no longer in PCM Library” to remove models. This also deletes any models that now may have DELETE as the alpha for the part. 4. The new cabinet codes will appear at the top of the list. Click the DontTest checkbox for those codes which will not be tested by this program (ex. BROC04C) 5. Once all DontTest codes are selected click “Add and Remove From Not Req” – this will add the new cabinet codes to the Not Req Price Column and Not Req by Style tables. Also the Not Req tables will have the cabinets removed that are marked DontTest. This step should be executed anytime a new cabinet is added or a DontTest checkbox is clicked later after deciding not to test a cabinet code. 6. Close the Testing form to go back to the Main Menu and then return back to Testing (this updates all screens in testing) 7. Enter the PBCode (code that appears in Pricebook# tables) to the blank cabinet entries. 8. If any new cabinets are bread board then go to the Options screen and enter the code in the Bread Board Assign table with the proper BB## code. 9. For cabinet codes that are style XX select the cabinet code and click on Selected Cabinet set for Style XX. This will set Not Req everywhere except for the NoStyle column is selected. 10. Finally go to the Not Req tab and select the proper not required boxes.

Generally speaking a cabinet gets it’s price from looking in VCabDataModels for the PBCode. PBCode is in the PriceBook# table that contains the price.

For the Quote program, a PBCode in the Blocks table places that group of models in the Quote program. The VCabDataModels table is used to determine what Models are included with that PBCode.

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 13 of 18 04/09/18 Prestige, Inc. Procedure’s BUILD

This screen is used to clear out information so that a new PCM library can be loaded back into it. There are four steps to rebuilding the Quote library.

1. GetPCMLibrary97 program downloads a new library. 2. PCMCompiler02 compiles the data ready to be downloaded into Quote. 3. The Clear MAT & GRP Tables and Code button is clicked to remove PCM info. 4. PCMCompiler02 copies new compiled library to Quote.

The Reattach button refreashes the links to the tables. If tables are blank then try reattaching.

EMAIL ADDRESSES This table contains the TO/CC email address when you email the test results. Enter the word “FAILED” as the Email Grp. Enter the email addess to send a copy of the failed results messages to. Click the check box if you want there name to appear in the TO section of the email. Leaving it unchecked will put there name in the CC section of the email. When the Email button is pressed on the Results page the address with the Email Grp FAILED will receive the failed results email message. BUILDING PRICEBOOKNEW 1. Go to the Test page and click Write PriceBookNew 2. Go to the GL page and click on all the PA thru PK and XX styles to test. 3. On the Test page the set and clear the following check boxes: Select Runs checked Save Segments unchecked Test Pricebook Only checked Failed Only unchecked Run Test Snapshot unchecked 4. Click on Run Styles To Test to start generation of PriceBookNew table 5. When tests are completed PriceBookNew table will be updated and the new pricebook can be generated by the PriceBook02.mdb program.

Notes: The TestPrice is place in PriceBookNew when test is completed. If the test failes then the price will have an asterisk placed at the end of the price.

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 14 of 18 04/09/18 Prestige, Inc. Procedure’s 1. HOW TO UPDATE THE PCM LIBRARY IN THE QUOTE PROGRAM 1. Start Program GetPCMLibrary97.mdb

2. Click On Clear PCM Data, click Yes to clear all data 3. When Finished click on Tools/Database Utilities/Compact Database 4. Click on Download PCM Data (this may take 20 minutes to complete) 5. Close Program 6. Start program Quote.mdb. 7. Go to the Testing screen and click on the Build tab

8. Click on “Clear MAT & Grp Tables and Code” (this may take a few minutes) Once this step is performed the Quote program will not work until this process is completed. 9. When Finished click on Tools/Database Utilities/Compact Database 10. Close the Quote.mdb program. 11. Start program PCMCompiler02.mdb

12. Click on “Clear MAT/GRP tables (this may take several minutes)

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 15 of 18 04/09/18 Prestige, Inc. Procedure’s 13. When Finished click on Tools/Database Utilities/Compact Database 14. Click on “Create TXT Files” (this may take from 10-20 minutes) 15. Click on “Copy To QUOTE.MDB” (this also takes several minutes) 16. When completed close this program, the Quote.mdb is now updated. HOW PRICE TESTING WORKS

Here is a basic outline on how price testing is performed.

1. All tests are selected that are required for the style column or style for the style being tested. 2. The first model is tested from the tests to run. 3. The number of passes are checked. If there is more than one then the first pass is performed. 4. GL option values are set from the GL screen 5. GL options ED, SDB, SDW and DRW5PC are set from the table Styles To Test. 6. The GL model is evaluated according to the options entered above. 7. The GL results are then assigned to the model under test. 8. The TestPrice is obtained from the evaluation of the model 9. The ElecPrice is obtained from the PriceBook#, where # is the PRICECODE segment. 10. The column to pull the price from is determined from the S and DRW5PC segments using the table under PriceCol. This can be overridden by the “.PC” segment in the Options/Model assignment list. 11. If the BB option is not blank then the bread board dollars are added to the ElecPrice using the Bread Board table under Options. 12. The (ElecPrice + BBPrice) * (1 + Price Increase) is set to the CompPrice (compare price) 13. If the CompPrice and TestPrice are within the Allowed Error then the test passes. 14. The results are written out to TestResults along with the segment results of the test 15. If the test has more than one pass then the next pass is incremented and the process is repeated starting at step 4. If there are no more runs then the next step is performed 16. The Run Test check box is cleared 17. The next model to in the run tests list is brought up to run next and the process goes back to step 4. C:\LOGQUOTE.TXT

This file contains some useful information. You can open this file during testing and it will give you the estimated time of completion of the testing.

ERROR MESSAGES IN THE LOGQUOTE FILE

The Price Column is not setup for style 'UP' w/5 piece '' go to PriceCol page and setup Style/Drw5pc and PriceColumn!

If this message appears then go to the PriceCol page and make an entry for the style/5 piece which is reported in the message. In this example the style UP with no 5 piece should be added with the PB price column.

C:\QUOTECMD.TXT

This file allows you to send commands to the Quote program while tests are running. Edit the file with NotePad and enter STOP in the first line if you want to stop the testing before it is finished. COMPACTING DATABASES The EnvironQuote program can also be used to compact databases.

Open the program and click on Compact Databases and all the databases listed will be compacted. DATABASES

QUOTE PROGRAM DATABASES QUOTE.MDB – the front end program for the order data, contains the pricing engine and the automated tester. QUOTEDATA.MDB – contains the customer master, option segments, product segments, order headers and line items. ENVIRONQUOTE.MDB – contains the environment variable for data locations and also can compact databases

SUPPORT DATABASES FOR AUTO TESTING TestTracking.mdb – stores test results and segment restuls for a test EmailAddr.mdb – stores the email address to email results to ValidationData.mdb – has options for pass numbers Pricebook.mdb – contains electronic pricebooks PricebookNew.mdb – electronic price book generated when writing pricebook PriceBookPaper.mdb – defines the paper copy of the pricebook, blocks for cabinet codes PriceChk.mdb – cabinet codes and standard options

SUPPORT DATABASES FOR COMPILING THE QUOTE PROGRAM

GetPCMData97.MDB – Retrieves all the PCM data from the AS400 PCMCompiler02.mdb – takes the data from GetPCMData97 and compiles TXT module files and acculates matrix tables data. Program also copies the new lib info to the Quote.mdb program.

CREATING AN INSTALL CD (FOR DEVELOPERS ENVIRONMENT ONLY) 1. Start Access 2002 with Quote.mdb 2. Clear the Quote data, debug mode, Setup/Init 3. Compact Quote and QuoteData databases 4. Reopen Quote.mdb 5. Design any module. 6. Click Add-Ins/Package Wizard 7. Verision = 1.0, second number is build number 8. Package should include these files: Quote.mdb QuoteData.mdb EnvironQuote.mdb DA02535.TLB DAO360.dll 8. Yes, include the access runtime, yes include system files, no need for Explorer 5.1

INSTALLATION NOTES

Sometimes the system will request a reboot on installation, sometimes multiple times. Seems to want to reboot more for Win98.

When multiple versions Access are installed the associate switches between versions. What ever the last version that was opened appears to be set to the default. In XP you can right mouse over an MDB and get an option to Open With and select the correct version. In Win98 you can use the default for one version of access in explorer and the other version you have to open Access itself first then select the mdb. You also can setup desktop icons to open the different Access versions, but you cant use the default you have to enter the entire directory into the icon link.

When you start the program the EnvironQuote.mdb will be reattached in the same directory as the Quote.mdb program. This allows moving the programs to different directories. The Quote, QuoteData and EnvironQuote programs need to be in the same directory. Advanced users will be able to change the QUOTE environment variable to attach to the QuoteData.mdb to allow for quote sharing.

When the program first starts there will be no data for orders or customer information. When New Quote is clicked a message will appear stating there is no default customer setup in the customer master. Clicking OK will bring up the customer master.

SETTING UP THE CUSTOMER MASTER 1. Enter the Ship To customer number and address 2. Enter the Sold To customer number and address 3. Setup the Trade and Cash discounts 4. Select this customer if it is the default customer

There is a Quote uninstall added to XP. There is no uninstall with Win98, but there is an uninstall MS Access 2002 Runtime. Also in Win98 you have to go to the Quote directory and manually delete the files.

The error “Path/File Access Error…” occurred when installing on Win98 computer. Clicked cancel and the Quote program seems to run fine.

The Quote.cab file contains all the databases. To update an install CD change the Quote.cab file provided only the mdb’s have changed.therrmann

D:\Docs\2018-01-08\0a8a6390526da9143d1e0e84a36236f8.doc Page 18 of 18