Error Messages with Numbers

17.4.1 File does not exist (error 1)

• The file pc/MRP is trying to find does not exist. This often occurs if you have selected a custom printout that does not exist instead of a standard printout. If you are running the audit BOM program and the missing file is BOMUPD.MEM, run the cost roll up option in inventory to generate a new BOMUPD.MEM. If you are trying to enter or edit the address log book and get this error msg you have deleted a file named BLKEDIT.WRI and must restore this file to the pcmrpw directory. Another file that is often deleted is BOMTEMP.DBF. This file is necessary to print out BOMs and can be restored from a backup.
• This error may also occur, if you have activated Audit Trail Module, with pc/MRP V6.53P, and are trying to edit a chart of accounts record. Call Software Arts for an upgrade to 6.54I or higher.
• pcmrpw.exe file is broken or corrupt, copy in a recent (same version) pcmrpw.exe file from a backup copy or pcmrpupd directory.
• Name of .FXP file that is causing the error msg starts with FIND indicating pc/MRP can't find an index file. Reindex the data base that pc/MRP is working or use pc/MRP's Configuration Module and run the Reindex all files option.
• pc/MRP's config.mem file may contain extra variables such as local.mem. Contact Software Arts for a copy CLRCONFG.EXE. Run CLRCONFG.EXE to clean up your config.mem file.
• If the error is "CLEANPATH DOES NOT EXIST," a library was not loaded or is corrupt. Reboot your computer and start again.
• If the error is because of a missing .fxp or .prg file reboot the computer. If that does not work, restore the pcmrpw.exe from a backup.
• If you are deleting an address id and answer Y to change everywhere and have not activated the infinite bucket module and have pc/MRP version 6.80as and lower, pc/MRP can not locate an action index. Update to the latest version of 6.80. If you have version 7.00, call Software Arts to walk you through entering following command line instructions:
• do checkdbf with "action.dbf"
• msg = "ACTION"
• do re-index

17.4.3 File in use (error 3)

• This error exists in versions 6.49BK to 6.54I. This error happens when the user try to invoice with inventory adjustment method set to P (Parts). To correct call Software Arts for update. For temporary fix, set inventory adjustment to A (Assemblies).
• Two users have logged in with the same name or no name and are printing or displaying a BOM. Logging in with the same name or no name causes both users to use the same temporary BOM file.
• Earlier versions of 6.73, 6.74 and 6.75 would leave the purchase dbf file open after printing out a receiver. Down load a manual update to version 6.73U, 6.74J or 6.75B or higher.
• If this error occurs while closing the month, reclose the month and be sure to select the last two GL reports to print or display. You can also update to 6.80AA or higher.
• If you are the one who caused the file in use error message, returning to the "Main Menu" will close the file and fix the problem.

17.4.4 End of file encountered (error 4)

• Re-index the related data base file(s)

17.4.5 Record out of range (error 5)

• Index file that pc/MRP is trying to use needs to be re-indexed. Go to pc/MRP's Configuration Menu and select "Re-index all files".
• The index file may be broken in such a manner that re-indexing does not help. In that case, the index file must be deleted. Call Software Arts for help in determining the name of the idx file to delete. (suspend with tag() in debug window)
• This error message can occur if you have an apostrophe or quote character(s) in your part number.

17.4.7 File you are attempting to rename already exists. (error 7)

• If you are removing records marked for deletion you do not have deletion rights or another user has ownership of the file or folder.

17.4.10 Syntax Error (error 10)

• If this message appears when you are trying to scroll a data base file. The field you are trying to scroll on is blank in every record in that data base file. Edit a record in that data base file and enter some data in the field you are trying to scroll on.
• If this error appears during a cost roll up or an audit BOM, search for and delete a inventory and or BOM record with a blank part or BOM number.
• If this error message occurs when you are scrolling, and it does not display the scroll window, it could be caused by an older version MSG.DBF. Call Software Arts and they will walk you through installing the correct MSG.DBF file.
• This error message can occur if you have a single user version 6.55x or lower, and have activated the Audit Trail Module and are editing a PO, sales order or quote line item. Update to version 6.55y or higher.

17.4.11 Invalid Function (error 11)

• Data base file structure has been altered by EXCEL. Delete the dbf file, restore from a back up copy and re-index new file.
• If this error occurs while you are running an exploded BOM, MRP or cost roll up report, check for a BOM calls itself, by running the "Audit BOM" report.
• pc/MRP has an invalid function in its source code, versions prior to 6.36AP had such an error when selecting sort by cost descending when running an inventory report.
• If a BOM has a part number without an A P or L in it's part_assy field and you are running a check availability report, this error can occur. Edit the part and add an A P or L to it's part_assy field.

17.4.12 Variable not found (error 12)

• This message will appear if pc/MRP can not find a memory variable. Call Software Arts if this message appears.
• If you install pc/MRP twice pc/MRP will report variable MFDRIVE not found. You must then run the CLRCONFIG.EXE program found in the pc/MRP directory. This file can also be downloaded from the troubleshoot section of our website www.pcmrp.com .
• If the missing memory variable is LEV, the BOMTEMP.DBF file has been overwritten and must be restored from a backup copy of BOMTEMP.DBF. The BOMTEMP.DBF file's first field is LEV.
• This error msg can appear if the data base file structure version does not match the pc/MRP's program version.
• If you are trying to delete a BOM and have version 6.54 through 6.55C and get a "MPARTNO not found", there is a bug in the code. Call Software Arts for an update to version 6.55D or higher.
• If you have pc/MRP version's 6.53P - 6.55D, have set the Stock Adjustment Method to P, entering an invoice and get a MSTKISSU not found. Call Software Arts for update to pc/MRP version 6.55E or higher.
• If you are using version 6.54 - 6.56 and the Variable AUSERSCROLL is not found, PCMRP was able to locate a .USR file with the same name in the PC.
  Enter PCMRP with another user name or rename the .USR file that the path is finding, enter PCMRP with your name, exit and restore the other .usr file.
• Issuing stock to manufacturing from the stock room module gives a Variable MSITEMNO not found error message.
  Always answer Y; there is a sales order or work order number that you are issuing parts for. Answer N (no sales/work order) will cause this error.
• If you are trying to print out a BOM, run Audit BOM procedure and then fix any errors it may have reported.
• If you are running Audit BOM and have version 6.73ap and get an "MBOMNO NOT FOUND," update to the latest version via our website (version 6.73ar or higher).
• If you are running pc/MRP version 6.73AW or lower and the variable is Module, then update to a later version or call Software Arts. (Control L Instructions, Public, Module, Module = " " cancel, make a non change edit to the configuration menu. Simply open and save.)
• If you are trying to open the Logbook in Inventory, (PROCEDURE PARTLOG PRPARTSC.FXP LINE 464 STRING VARIABLE NOT FOUND) select main menu to exit this error prompt. Re-enter inventory, Modules, Inventory, Edit, select Edit in the Action square. In View mode this error will occur on versions 6.80Y or older. In Edit mode this error will not occur.
• If you are trying to print out a report or form and get an "MCHIOCE NOT FOUND" and are running version 6.80 or 6.82 update to the newest revision of 6.80 or 6.82 available on the website.
• Could be an alpha character mismatch, update to the newest revision level of your version of pc/MRP or call Software Arts.
• If you are trying to print a PO delete that PO and try again.
• If the error occurs when you are entering or editing the address module you may have to delete one or more of the drop down address lists. Use configuration and settings and utilities to re-enter any blank lists.
• If you are trying to print a check with version 7.50J, and you get a variable MBAMT not found, post the month and reprint the check.

17.4.13 Alias (file name) (error 13)

• Version 6.55G would display this error Alias QUOTE not found if you were entering a work order and changed the work order number issued. Call Software Arts and update to version 6.55H or higher.
• Versions 6.73Z and lower will display this error, call Software Arts and update to version 6.73AA or higher.

17.4.15 Not a table/dbf file (error 15)

• Database file that pc/MRP is trying to open is corrupt. This can be caused by hitting the reset button, turning off power or hitting the escape key when pc/MRP is in the middle writing to a dbf file. Call Software Arts before proceeding with the instructions below.
• If the dbf file is a temporary file (ACTION, ADDLBTMP, ADJLABEL, AUDITSN, AUDITMP, AVLDATA, BILLING, BILLTMP, BOMTEMP, CONSOL, COSTSALE, CYCTMP, DUPPART, ARSLSDST, ARSLSTRX, FIFOTMP, MAKECONS, MOVEMENT, MRPTMP, MRP2CONS, PPVTMP, PRGLTMP, PRTRNTMP, SANAL, TEMPECN, TEMPEST, TEMPSHRT) restore from a backup. If you have pc/MRP version 6.77f and higher, pc/MRP will intercept the error message and automatically recreate the dbf file.
• If the dbf file is a pc/MRP administrative file (ERROR, DATASTRU, MENU, MSG) restore from a backup. If you have pc/MRP version 7.00 and higher you can delete the file (Restarting pc/MRP will recreate the file).
• If the dbf file is a pc/MRP main data file (ACTMPLT, ADDRBOOK, BOM, CHARTACC, ECN, INVOICE, LABOR, PARTMAST, PURCHASE, REQUEST, RECEIVE, RTMPLATE, SALES, QUOTE, SNLOTDET, SNLOT, STAXENT, STOCKTRA, TRAIL, TRANSACT, ALTCUR, USERSETS, ROUTING) restore from a backup or use Norton's File Fix program to fix the data base file or send the file to Software Arts for repair. If you have pc/MRP version 7.00 or higher and delete ACTMPLT or CHARTACC, pc/MRP will recreate the file with pc/MRP's original account numbers in them. Do not delete these files if you have added or edited pc/MRP's chart of account numbers or you have closed prior months.
• If the dbf file is your password data file restore from a backup. If you have pc/MRP version 6.82P or higher you can call Software Arts for an authorization code to re-create the file with one user MASTER with a password of MASTER. If you choose to re-create the file you will have to re-enter all of your user names, passwords and module rights.
• The Software Arts technician may ask you to press control F11 and look for a memory variable named mdbfname that contains the name of the corrupt dbf file.
• Delete all of the index file associated with that database file and then reindex. Call Software Arts for the name of the indexes to delete.

17.4.16 Unrecognized Command Verb (error 16)

• Programming error. Call Software Arts at 408-226-7321 or update to version 6.78m or higher.

17.4.22 To Many Variables (error 22)

• To many line items.  Select SINGLE for REVIEW when editing.

17.4.26 Table is not ordered (error 26)

• Somebody has created a cdx file with the same name as a pc/MRP idx(index) file. Call Software Arts for instructions on deleting the cdx file.
• RAM memory has become corrupt or network delivered a corrupt exe file. Reboot the computer and try again.
• Reindex, option 27 in the settings and utilities.

17.4.30 Position is off screen (error 30)

• A row or column number is off the current screen. Versions prior to 6.36T and 6.49F would display this error message if you selected address book reports and then selected work order reports. This error can occur when the Windows 95 start bar is moved to the top of the screen (move the start bar to the bottom of the screen)
• The foxfont.fon file is missing or corrupt. Restore the foxfont.fon file.
• Another FoxPro application is active and is using the pc/MRP FoxFont.fon font.

17.4.31 Invalid Subscript Reference (error 31)

• Reboot the computer.
• Document being edited has an invalid document number. Call Software Arts to change the document number through the Ctrl-L function.
• The area.mem file contains quote marks in one of the area names. Remove the quote marks.
• A lower case letter exists in the document number. Call Software Arts to correct this, unless you want to try and find the lower case letter yourself. For Example (replace all SONO with upper)
• Re-index. Option 27 in the Settings and Utilities.
• Data you are importing from Excel has an invalid field name, Column (field) names must be alpha or numeric only, 10 characters or less.

17.4.36 Unrecognized phrase/keyword in command (error 36)

• Versions 6.54 - 6.55H could display this error msg if you enter your name as two words with a space in between the two words. Enter your name as one word, such as Jim or Smith or JSmith.
• If you are updating from pc/MRP version 6.55 or lower, the update may be trying to copy .wri files. Restore from the backup directory, pcmrpwbk. Use Window's Find Option, to find and copy all PO*.wri files in the pcmrpw directory into a purlogs subdirectory. Delete all the PO*.wri files pcmrpw directory. Next copy all remaining *.wri flies into an addrlogs subdirectory. Delete all *.wri files in the pcmrpw directory. Finally, rerun the update program.
• If you are trying to run an Addressbook report and get an error 36 on version 6.80AN or lower, update to the newest revision of 6.80.
• If pc/MRP is trying to create a temporary file with a use &mfile or copy structure to &mfile command and the path or file name has spaces in it, update to version 7.43c or higher (use (mfile) and copy structure to (mfile).

17.4.39 Numeric Overflow (error 39)

• Data has been added to a pc/MRP dbf file from another program such as EXCEL causing numeric overflow in one of the fields in that file. Use option 41 in the settings and utilities to zero out the overflow. Users can also use dBASE or Foxpro's replace command to load valid values into that field.

17.4.41 Invalid or missing memo file (Error 41)

• Memo file (dbt file) is missing or invalid. If it is missing call Software Arts to restore the associated dbf and dbt files from the backup (rename dbf and dbt file, use renamed file, copy to orig file name type foxplus, use and re-index). If it is not missing and you have Versions 6.80m or higher, or 6.82g or higher you can determine the corrupt file by pressing CTRL F10. This opens a .txt file. Here search for the "Currently Selected Table." The .dbf file listed directly under this heading is the corrupt file. You can now run Option 43 from the Settings and Utilities on this file and the file will be fixed. If you have an older version of pc/MRP or if this does not work call Software Arts for instructions on renaming the associated dbf and dbt files. Use the renamed files and "copy to" the original name of the files, type foxplus.
• With versions 6.80L and lower if you run option 43 the files created will be called msourcef.dbf and msourcef.dbt. You will then need to rename these files to their original names.

17.4.43 Insufficient memory (Error 43)

• Insufficient RAM memory, requires 8 meg
• If this error occurs while editing a PO or sales order, the PO or sales order has too many line items. Increase the RAM memory on that workstation and/or add the line memlimit=60 to your config.fpw file using notepad. To limit the number of line items per PO or SO select option 63 in the settings and utilities.
• If this error occurs while running a cost roll up or generating an MRP, run the "Audit BOM" option. (Modules, Bill of Materials, Audit BOM) The audit option will check the BOM module for a BOM that calls itself. It will display a list of errors in the Bill of Materials module. Correct the errors and the cost roll up or MRP should run correctly.
• You are running too many executable programs at the same time, close all programs, reboot and try running pc/MRP by itself.
• Run clrconfg.exe
• Restore the related database file(s) from a backup.

17.4.50 Report file invalid (Error 50)

• Report file was not updated to updated incorrectly. Call Software Arts for the name of the report file. Then copy over the correct .FRX and .FRT file from the PCMRPUPD dir to the PCMRPW directory.
• Related index files may need re-indexing.
• If you get this error when you are attempting to modify a report in version 7.41 and higher using option 24, this may be a 16-bit report. Call Software Arts to run: Do RPTCON60.EXE with "FORMNAME.FRX", "REPORT", "FOX",.T.

17.4.52 No data base file in use (Error 52)

• If you are running an MRP report and a BOM exists in the partmaster but not in the BOM file and you hit continue after the warning msg you can get this error.

17.4.55 Memory variable file is invalid (Error 55)

• .mem file is broken or corrupt. Call Software Arts to get the name of the file and copy in a new .mem file from a recent backup or the pcmrpupd directory. If the file is a local.mem file it can be deleted. pc/MRP will create a new file.

17.4.107 Operator/Operand type mismatch (Error 107)

• A character field was imported as a numeric field or a numeric field was imported as a character field. Correct the field type and import the data again.
• If you are running pc/MRP's MRP Consolidation Report with trace calculations on, set trace calculations to off and/or update to 6.73n or 6.74 or higher.

17.4.108 File in use (Error 108)

• File with same name in another directory connected by the path statement is in use. This can happen with pc/MRP's .USR files. Assign the user another name for logging into pc/MRP.

17.4.109 File in use (Error 109)

• File is in use by another. Reboot the server.

17.4.110 Exclusive open of file is required (Error 110)

• Somebody else is using the file. Wait until they are finished.
• File was left open when somebody shut off power to their PC. Get everybody off the network and reboot the server.
• You have two copies of pc/MRP open on your PC. Quit one of the copies of pc/MRP.

17.4.111 Can not write to a read only file (Error 111)

• File has been attributed read only. Attribute the file read/write ATTRIB -R [Rtn]. In the multi user version of pc/MRP for Windows, there are only 7 files that should be attributed read only (pcmrpw.exe, startmrp.exe, config.fpw, foxfont.fon, foxtolls.fll, foxw2600.esl, msg.dbf,).
• This error msg may appear with a Sun server running SFT. If so have everybody log in to the under one user's name.
• This error message can occur if you have opened the drive and or directory shared as read only instead of full rights. In Windows 95 you must share the directory as well as the drive.
• Another program, such as Excel. is using the .DBF file pc/MRP is trying to access. Close down the program.
• Tape backup failure can leave a file locked, get everybody off the network and reboot the server.
• The user does not have network permissions to modify the related file.

17.4.112 Invalid key length (Error 112)

• The product code size and suffix size = or exceed the length of the entire part number. Decrease the product code and or suffix size.

17.4.114 Index does not match table file (Error 114)

• Index is broken. Rebuild the index by reindexing.
• For versions 6.80 and beyond if this occurs while trying to log-on to pc/MRP, delete the MSG.IDX. If you are using the Advanced Password module delete both the MSG.IDX and the BYPWUSER.IDX.

17.4.125 Error 125

• Printer is configured as a network printer when it is actually a local printer. Reconfigure the printer as a local printer.

17.4.202 Invalid path or filename (Error 202)

• pcmrpw directory is hidden.
• Network has lost connection with the server.
• BOMUP.MEM contains the wrong default directory. Delete the BOMUP.MEM or do a cost roll-up.
• CONFIG.MEM file conatins the wrong default directory. Run CLRCONFIG.EXE.
• If your computer does not have a C: drive (windows terminal workstation) select main menu and cintinue to use pc/MRP.

17.4.214 Window has not been defined (error 214)

• A window has not been defined or removed from memory. Versions prior to 6.36T and 6.49F would display this error message if you selected address book reports and then selected work order reports.

17.4.356 Invalid Macro Key File Format (error 356)

• An attempt has been made to use a macro file with invalid data. Delete all files with an "fky" extension except the macro.fky. If that does not fix the problem restore the macro.fky file from a backup.

17.4.1000 Internal inconsistency error (error 1000)

• Go to the Utility Module and run Option 27. Reindex all files.

17.4.1102 Can Not Create File (error 1102)

• pc/MRP may be trying to install a barcode font, the foxfont.fon, or the SAHTML driver.  Try logging into this computer as an administrator.   If this error occurs with the barcode fonts, go to the control panel and select to add/remove fonts.  Then select the fonts from the pcmrpw\barfont folder.  Administration rights may be needed to download and install these fonts.

17.4.1103 Seek read error (error 1103)

• A general fault protection error may have occurred. Exit Windows, shut down the computer, restart the computer and pc/MRP.

17.4.1104 Can not read file (error 1104)

• File is sitting on a bad sector use Norton's Disk Doctor or Microsoft's Scandisk to move data and mark out bad sector.

17.4.1105 File write error. (error 1105)

• Hard disk is full.

17.4.1108 Picture too big or wrong format (error 1108)

• A picture has been loaded into memory and is corrupt. Reboot computer. If clrmem2.fxp is displayed it could be the pcmrpw.bmp file.

17.4.1231 Missing operand (error 1231)

• A report is missing a condition parameter. Versions 6.55AA and lower had this problem when sales and quote reports were sorted or specified by salesman. Update to version 6.55AB

17.4.1234 Subscript out of bounds (error 1234)

• RAM may have caused error, exit pc/MRP and Windows, reboot and try again.
• pc/MRP has a bad user file (.USR file in versions 6.55 or lower and .USM file in versions 6.56 and higher). Delete the broken user file (it will have the person's login name followed by the extension .USR or .USM). Also delete the default.usm file so that pc/MRP will recreate the default.usm file. Re-enter pc/MRP under that person's login name and pc/MRP will automatically create a new user file.
• PCMRPW.EXE file has been corrupted, install a new copy of PCMRPW.EXE (must be from same version).
• Database file has been modified. Select configuration then select settings and utilities, press the next button, select option 39, print out the file structure of the database file involved and call Software Arts.

17.4.1282 Insufficient memory (error 1282)

·  Windows does not have enough memory left to run pc/MRP for Windows.

• Make sure your workstation has at least 8 megabytes of RAM
• Close any programs that are running concurrently with pc/MRP
• Make sure your hard disk has a large permanent swap file (10-30M)
• Your computer may not contain enough RAM. Add the line memlimit=60 to the config.fpw file. Config.fpw is a text file that can be modified with notepad.

17.4.1405 Run Command Failed(error 1405)

• The directory is mapped as a drive. pc/MRP current update programs do not have this problem.
• If you are running the update through pc Anywhere and this error occurs, first run pcmrpupd.exe directly from explorer and then pcmrpw.exe.

17.4.1691 Library file is invalid (error 1691)

• Library file has become corrupt in memory, exit pc/MRP and restart your computer.
• Check the network for hub collisions. The hub light will go yellow or red when it is being used if there is a collision. Disconnect the workstation causing the collisions from the hub.

17.4.1705 File Access Denied (error 1705)

• Somebody else is using the file, the operation you are running requires exclusive use of the files, get everybody out of the file and try again.
• File is protected by the MSDOS attrib command. At the DOS prompt attribute the file read/write by entering ATTRIB -R .
• Exit out of windows, and re-enter windows
• If you have a NET.CFG = or SHELL.CFG, make sure the FILE HANDLES statement reads FILE HANDLES = 99
• Another application or program such as FOXPRO, R&R Report Writer or dBASE has opened the file for exclusive use
• You are trying to run a single user version of pc/MRP on a network as a multi-user product and either you have a second copy of pc/MRP open or another user has a copy of pc/MRP open.
• You are running a multi-user version of pc/MRP using Novell networking software and you have not flagged the five files sharable read only.
  Flag the 7 files CONFIG.FPW, MSG.DBF, FOXFONT.FON, PCMRPW.EXE, STARTMRP.EXE, FOXTOOLS.FLL FOXW2600.ESL SRO (sharable read only).
• Versions 6.55E - 6.55F would display this error msg because the second user cannot find msg.idx and msg.dbf is in use by the first user.
  Call Software Arts and upgrade to pc/MRP version 6.55G as it adds the trailing \ to the default directory.
• Somebody turned off power while in pc/MRP after they locked a file or record. Users can either Reboot the server or kick off the user that has the locked file through the server. Get everybody logged out of the server. The quick fix is to reboot the server. Make sure however everyone is logged-off of the server. Then and only then, shut off the server and power it back up again. The file and or record will be unlocked. If you opt to kick the user off that has the locked file, and you have Windows NT Server, go to the server, select start, programs, admin tools. Select server manager and double click on the server. Select "In use" and close the pc/MRP resource. Another way to get to the "In Use" screen and kick users off a certain file is to click on the "Start" button, select "Settings", select "Control Panel", double click on the Server icon, and click on the "In Use" button. If that does not fix this error then you will have to reboot the server. Once again, make sure everyone is logged off of the server if you choose to reboot. If you have windows 2000 server, goto the control panel, select Admin Tools, Computer Management, system tools, shared folders, open files, and close the locked file.
• With the BOM module, if two people try to print out a BOM at the same time and both have logged in with the same name, the second person will get an error 1705. To prevent this, have everybody log in under a different name (mikes and mikeh instead of mike and mike)
• If error 1705 occurs with an index file, delete the index file and then rebuild it by re-indexing that file.
• You do not have full rights (read, write, delete) to the pcmrpw directory. The pcmrpw directory and or the directory(s) above the pcmrpw directory have not been shared as full share directorys. Although the drive containing the pcmrpw directory may show full control to everyone, the pcmrpw directory itself may have less than full control rights to some files. To correct this situation open explorer and right click on the pcmrpw directory, select properties, select security (available on NTSF formated drives only), select permissions, select full control, check both the "Replace permissions on sub directories" and "Replace existing permissions" check boxes. Click on the OK button and Windows will give full control to all users for all files within pc/MRP.
• You have restored from a backup CD ROM and all files are attributed read only. Unattribute all files by using the ATTRIB *.* - R command in DOS or highlighting all files, right clicking, selecting properties, and un-check read only. You will have to go back and re-attribute a few files read only for 95 networks as specified in chapter 15.5.1.
• If you get this error when starting up, delete a file called local.mem and reboot.
• If you get this error while trying to scan for your browser, you do not have rights to write to your local windows directory.

17.4.1705 File Access Denied for Older Networks such as Invisible, Lantastic, and Windows for Workgroups(error 1705)

• On a work station or single user machine, increase the number of files= statement to 100 in your config.sys file in the root directory, reboot and try again.
• If you have a multi-user copy of pc/MRP, make sure share is loaded in the server's AUTOEXEC.BAT file with 500 locks SHARE.EXE /F:5120 /L:500
• If share is loaded into a single user machine, make sure share is loaded into the AUTOEXEC.BAT file with 500 locks SHARE.EXE /F:5120 /L:500

17.4.1707 Structural .CDX file not found (error 1707)

• User has created a .CDX index file for a .DBF file. Delete the associated .CDX file and re-index.

17.4.1958 Error Loading Print Driver (error 1958)

• Try rebooting the client PC. If the error persists reboot the server and/or un-install and re-install the print driver.