Error Messages without Numbers

17.5.1 Watcom WIN386 not running on a 386 DPI implementation error msg appears

• Try starting Windows with WIN/D:X command instead of WIN. If that works modify the emm386 line in your config.sys file to read: DEVICE=C:\WINDOWS\EMM386 NOEMS I=E000-EFFF

17.5.2 pc/MRP says Record does not exist

• Record may start with one or more blank characters. If possible change the field so that it starts with valid characters and not blank characters. Version 6.36AE and higher began to correct this problem by replacing FINDs with SEEKS.
• Part number size in configuration menu option 28 is set higher than 15. Reset it to 15 characters or lower.
• Item you are searching for has one or more blank characters. Scroll to the top of the screen to see if it is there. Once you have found it correct the error by editing the item you are searching for; find where it should be and or what it should be and change it so there are no blank characters.

17.5.3 pc/MRP says Can not save record, record has been edited by another

• The pc/MRP dbf file has a numeric overflow in one of the fields.
  Use dBASE or Foxpro for Windows to replace the field with valid values.
• Use option 42 in configuration settings and utilities to zero out the overflow. This is usually caused by a PO ration of 0 (Zero) in Inventory.

17.5.4 Can not bring up a record (partnumber with a lower case alpha character) from the scroll list

• This problem occurs on or around version 6.55H - 6.55K.
  Call Software Arts for update to 6.55M.

17.5.5 pc/MRP for Windows brings up a blank record instead of the record you selected

• Record may start with one or more blank characters. If possible change the field so that it starts with valid characters and not blank characters. Version 6.36AE and higher began to correct this problem by replacing FINDs with SEEKS.

17.5.6 Address and PO log book files keep asking if you wish to convert the files

• When you get to the save window, select save as WRI files.

17.5.7 pc/MRP for Windows requires excessive key strokes to process records

• Make sure the msg time-out time in pc/MRP's configuration menu is set at 1 or 2 seconds and not 0 seconds. With the Windows version of pc/MRP, setting the time-out time to 0 seconds leaves quantity adjustment messages on your screen indefinitely until you hit any key to continue.

17.5.8 Variable not found

• If pc/MRP for Windows is closing the month and the variable not found is MDUMMY, the chart of accounts has a record in it with an illegal account type code. The chart of account record number will be displayed at the bottom of the screen. Edit the record an fill in the account type field with a legal account type code.

17.5.9 Dialog box asks "Overwrite invalid foxuser file"

• Answer Yes to this question as a new empty foxuser file will not hurt anything.

17.5.10 pc/MRP freezes up

• If two people are entering sales quotes at the same time and the second computer freezes up, version 6.49BK and 6.53T and lower do not increment the quote number.

Corrective action:

Call Software Arts for update.

17.5.11 Internal Inconsistency Error Message

• Video driver is incompatible with FoxPro for Windows, change to a standard VGA driver and see if that solves the problem.
• Reindex the database file that is being used when the error occurs.

17.5.12 Stack Fault Error Message

• This message can be caused by a broken index file. Reindex the database file that is being used when the error occurs.

17.5.13 Letter of Floppy Drive You Are Installing From Message.

• You are trying to run pc/MRP from network neighborhood. Run pc/MRP from Explorer from a mapped drive. Within "My Computer", locate the PCMRPW directory and double click on the STARTMRP.EXE application file.
• pc/MRP is unable to locate the config.mem file within the pcmrpw directory. Delete a file named locate.mem (contains the name of the drive and directory pc/MRP is located in) and restart pc/MRP. This will create a new locate.mem file with the correct drive and directory name.

17.5.14 Macro Overflow.

• Macro file has become corrupt or tool long, delete the macro file "username.fky" or re-enter the macro you are running.

17.5.15 Library file is invalid

• Library file has become corrupt in memory, exit pc/MRP and restart your computer.

17.5.16 Record has been edited by another.

• Somebody has edited and saved the record since the last time you opened the record for editing. Edit the record again.
• One of the fields has a numeric overflow (all stars in the field). With pc/MRP version 6.80, call Software Arts for instructions on running overflow.prg. With pc/MRP version 6.82 and higher, run option 41 in the configuration settings and utilities menu to zero out the fields that have overflowed

17.5.17 Cost roll-up and exploded BOMs contain incorrect dollar amounts.

• If you are using a language other than English, use note pad to add the line: Point = "." to the config.fpw file in the pcmrpw dir.

17.5.18 Can not edit a document.

• User selected VIEW instead of EDIT under ACTION.
• The Advanced Password module is activated and the user does not have edit/create rights to the module.

17.5.19 Can not delete a document.

• User selected VIEW rather than EDIT.
• The Advanced Password module is activated and the user does not have edit/delete rights to the module. In version 6.77a and higher the user must have delete rights if the Advanced Password module is activated.

17.5.20 Highlighting a part in a BOM displays another partnumber.

• The BOM has duplicate part numbers. Edit the BOM and change the item number of one of the effected parts.

17.5.21 MSG.DBF does not have an entry for (Name of menu item.)

• pc/MRP's MSG.IDX file has become corrupt. Exit pc/MRP and use explorer to locate and delete the MSG.IDX file. Re-enter. pc/MRP will recreate the MSG.IDX file automatically.

17.5.22 Running option 43, Repair invalid memo file, deletes the file being repaired.

• pc/MRP versions 6.80k and lower contained this bug. The file that was selected to be fixed was renamed, msourcef.dbf. Rename msourcef.dbf back to the original name and download an update to a later version of pc/MRP.

17.5.23 pc/MRP field contains nothing but asterisks or stars (numeric overflow).

• Latest versions of 6.73 and higher contain a special program named overflow. This program allows the user to select a DBF field and zero out the overflow. Call Software Arts for instructions on running this program.

17.5.24 When scrolling for something (Inventory or BOMs), pressing enter does not open the selected file.

• The user FKY file has been corrupted. Find the user FKY file, their login name with an .FKY extension and delete this file. All macros and personal save settings will be deleted for this user.

17.5.25 Dates contain day and month, but are missing the century after updating to a Y2K version of pc/MRP.

• Call Software Arts to receive an update to pc/MRP, version 7.01C or higher, or to receive a file named fixcent.exe. To apply fixcent.exe, make a backup up pcMRP and then copy fixcent into the directory where pcMRP resides. Double click on the fixcent.exe file that resides in your pcmrpw directory and this will fix your missing century dates.

17.5.26 Insufficient memory when editing Address Book.

• Go to the Configuration Settings & Utilities Option 52 to edit every text files. If a message come up indicating the file is too big to open in note pad, that is the file causing the problem. Go to the window explorer to rename the file to another file name and go back to the Configuration Settings & Utilities Option 52 to recreate the file.

17.5.27 Part number in a BOM is not Issued when Running the Stockroom Issue Function.

• The partnumber in inventory is checked as being floor stock. Un-check the floor stock check box.

17.5.28 When printing a BOM an incorrect part number displays or prints out in every BOM.

• The BOMTEMP.DBF contains a record with this part number in it. Call Software Arts for instructions on how to ZAP the BOMTEMP.dbf file.

17.5.29 Browser location changes for everybody when individual user changes his browser location.

• Browser location is stored in local windows directory on workstation in a file named BROWSMRP.UMF. Network maybe setup such that server contains the windows directory. Mark the BROWSMRP.UMF file read only in the server's windows directory. You can change the browser used to open the module. You can also open the BROWSMRP.UMF file with notepad but do not change it.

17.5.30 A Bill of Materials Became mixed-up after Entering and or Editing the BOM.

• Version 7.40 through 7.43 and or updating from these versions could leave one or more BOM records with a blank ID. To fix this, enter the following command in the command line: use BOM index bomkey[enter]fillguid()[enter].

17.5.31 Can not open or locate Visual FoxPro Library File

• Restore VFP6R.DLL and or VFP6RENU.DLL from a backup copy if either of these two library files are missing.

17.5.32 Class not registered error message

When pc/MRP needs to use a class library .DLL or .OCX file, the operating system will first look in the registry, if it finds an entry in the registry pointing to where the .DLL or .OCX file is located and that file does not exist, the operating system will throw an error message. If it does not find an entry in the registry it will look in pc/MRP’s home directory. If it does not find the .DLL or .OCX file there, it will look in the system folders. If it does not find it in the system folders, it will throw an error message.

pc/MRP versions 7.50 and higher use the following DLL files, VFP6R.DLL and VFP6RENU.DLL

pc/MRP versions 7.52 and higher use the following .OCX files, MSCOMCT2.OCX (Date Picker), CTSCTSCHEDULE.OCX, TIME LINE OCX (MRP Timeline Report), CTTABS.OCX, CTTIPS.OCX

pc/MRP version 7.83 added MSCCOMCTL.OCX ( Tree View for Corporate Reporting)

To fix the problem you could do the following. (1) Copy the missing file into the directory the registry indicates it should be in. (2) Copy the missing file into the System32 folder or the System folder (Win 98 and 98). (3) Open up Explorer, find the file, leave the Explorer window open, Click on the Start button, Select Run and register it by typing in REGSVR32 and drag and drop the file from explorer into the run command line one space after the word REGSVR32. Be aware if you move this file be aware your computer may not be able to find it. If you are going to delete some of the registry entries, make a backup of the registry by selecting export and giving it a name to import it back in from if necessary.

Other cures might include disabling a virus checker that is not allowing un-registered DLLs to run or an operating system doing the same.