MSS
from IndustriOS Software
|
|
BOMP is Installed and Setup Improperly BOMP.MDB file is Closed Improperly Multiple Versions of Btrieve I am receiving a "BOMP Error 381 -- Invalid Property Array Index"? I am receiving a "BOMP Reserved Error (-8194)"? My Computer hangs in BOMP's Transaction Entry or Explosion Report? The BOMP Explosion Report is not exploding all of the sub-Assembly Items on the parent BOM? How do I fix error message 3141 in Transaction Entry and Bom Entry? Why can't I use the page up, page down and arrow keys on the lookup windows? Why doesn't the Convert from Platinum Utility display the conversion progress? How do I fix (error 5000) when posting transactions? Why I am receiving a "Run-time error 5" when validating my bom in Bill of Material Maintenance? Why do I have blank lines in my bill of material? Why are my components not being updated in PFW/PFD when posting? Why is Transaction Posting freezing my system? Why is the serial number field not allowing a full 30 characters? Why I am receiving an Error 3134 when using the WIP Commit transaction? Why are posted transactions causing my PFW/PFD cost layers to go negative? I am receiving file corruption or database is out of date
errors. How do I solve corruption errors and why do they occur? The Bill of Materials Processor's data is stored in a Microsoft Access database. Corruption errors occur when the BOMP.MDB becomes damaged and the data is unstable. The utilities that are used to fix corrupted data in the BOMP.MDB are found in the Utilities-DataBase Menu. It is critical to back-up the BOMP.MDB file and make sure all users have exited the BOMP before attempting to process any of the utilities. It is also very important to follow the instructions outlined in the BOMP Manual. This error can occur for multiple reasons, the following details the most common reasons. BOMP is Installed and Setup Improperly Double check each workstation and be sure the Bill of Materials and other MSS products have been installed and setup correctly. We require that our programs are installed on the server and not on individual hard-drives. File corruption occurs if the workstations are using a different version of BOMP or if one workstation is setup incorrectly. Installing to the server ensures that all users are accessing the same version. When installing to the server be sure BOMP does not exist on any local drives. Double check the Company Setup on each workstation to be sure the path setup is correct. If you have purchased multiple copies of our software and the program is installed on each workstation's hard drive double check the program file dates and be sure all files match from workstation to workstation. BOMP.MDB file is Closed Improperly Improper closing of the BOMP.MDB caused by power outages and fluctuations, disk or network failures, and/or shutting down Windows without exiting from BOMP. Be sure all users know the proper procedure to exit Programs and Microsoft Windows. Always use the Exit buttons included in the BOMP program screens. Using the Microsoft closing feature can cause GPF or freeze some workstations. All users should know and use the following procedure if their system becomes unstable or shuts down while BOMP is running:
Multiple versions of Btrieve are being run from BOMP workstations or Btrieve is not configured properly. This is the most common cause of BOMP and PFW/PFD file corruption. It is very important that you know how Btrieve is setup and which version should be running. We have a lot of old part numbers in bill of materials
that we are no longer using. The problem is that we need to track the history
of the items in PFW/PFD for at least one year. Is there a way to purge legacy
data from the live database? BOMP's transaction history is stored in three tables in the BOMP.MDB (History Detail, History Header, and History Serial), these tables do not store the BOM information, however, the tables do store the transaction history. You can use our Purge Database Utility to purge the history tables into a new database, auto-generated as BOMPHIST.MDB. This removes all completed transactions from the BOMP.MDB and stores them in the BOMPHIST.MDB. BOMP's Production Work Order Report and Transaction Status Report have an option to "link to history data", which allows you to report transaction information from the BOMPHIST.MDB. If storing the transaction history keeps enough of a paper trail, you could then remove all obsolete BOM's from the BOMP.MDB. Although the PFW/PFD Inventory Items would still exist in PFW/PFD. Your PFW/PFD Consultant may have some options of controlling PFW/PFD Inventory.
How do I modify an existing BOM? I have created a new
assembly and added the components. I noticed a missing item, went back into
the assembly and added the item to the component list. When I try to save it,
I get a message "Assembly already exists" and it WILL NOT accept
the change. I even tried deleting the assembly, but my delete button is
inactive.
In order to modify an existing BOM, you have to zoom and pull in the BOM from the "Assembly Key" top scroll bar. This zoom displays all current BOM's. You can not zoom on the magnifying glass next to the Assembly Key, type in a location and then make the change. A good way to check is if the Assembly has been pulled in correctly the assembly key and location will be grayed out. At this point you can click on the component tab, make the change and then save the BOM. You may also delete the entire Assembly. This occurs because the BOM is unique to the Assembly Key+Location Key, and you have to display the BOM record before modifying it. I am receiving a "BOMP Error 381 -- Invalid Property Array Index"? This error occurs because the previously saved custom table layout is no longer valid in the new version. For an immediate fix enter the program under a different user name. For a permanent fix, run the Repair and the Refresh options under Database Utilities. I am receiving a "BOMP Reserved Error (-8194)"? This message will be received if the user is trying to run the Repair utility and another user is in the BOMP system. All users must exit out of the BOMP system before a repair can be successfully run. My Computer hangs in BOMP's
Transaction Entry or Explosion Report? This is most likely caused by a "circular reference" in the bill of material. That means that a sub-assembly has itself as a component somewhere in the BOM. To test if this is the case, run the explosion report and enter a lower level number (3 is a good number). If the explosion report is able to complete with a lower level number and not with a higher number, then this is most likely the case. I am receiving a "BOMP Error (3426) This Action was
cancelled by an associated object in Move_Components."? This error is a know bug and was fixed in BOMP Version 3.01. The BOMP Explosion Report is not exploding all of the
sub-Assembly Items on the parent BOM? This problem is caused because the BOM's are
specific to the Assembly Key + the Location Key; therefore a BOM must exist
for the proper location. If a BOM does not exist for the Assembly Key +
Location Key, then the combination is How do I fix error message 3141 in Transaction Entry and
Bom Entry? This error was caused by a bug in the system and was fixed in version 3.10. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Why can't I use the page up, page down and arrow keys on
the lookup windows? This error was caused by a bug in the system and was fixed in version 3.10. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Why doesn't the Convert from Platinum Utility display the
conversion progress? This error was caused by a bug in the system and was fixed in version 3.11. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. How do I fix (error 5000) when posting transactions? This error occurs when you have an Additional Cost item as the first component on the bill of material. Using the detail screen of Transaction Entry you can move the item to the bottom of the bom. You would then need to change the standard bom, so the error doesn't occur in future transactions. This error was caused by a bug in the system and was fixed in version 3.11. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Why I am receiving a "Run-time error 5" when
validating my bom in Bill of Material Maintenance? The Bill of Materials Maintenance program will display a "Run-time error 5" while validating the BOM if the first item is an additional cost item. This error was caused by a bug in the system and was fixed in version 3.2. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. I am receiving an Error 3426 when entering a scrap value
in the Bill of Material Maintenance program. This error was caused by a bug in the system and was fixed in version 3.11. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. When I zoom on the GL Account Number in the Additional
Cost Maintenance, Overhead Maintenance, Burden Maintenance programs the
lookup pulls the sub system key (8 characters) instead of the account number
(32 characters). How do I pull in the full account number? This error was caused by a bug in the system and was fixed in version 3.2. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Why do I have blank lines in my bill of material? A blank line was being added in Transaction Entry and Bill of Material Maintenance, when entering Additional Cost, or Standard Text items. A blank line was also added if a new line was selected but an item was not entered. This error was caused by a bug in the system and was fixed in version 3.2. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Why are my components not being updated in PFW/PFD when
posting? This error was caused by a database bug in the system and was fixed in version 3.21. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. If you have a later version and all component items are not being updated, then double check that the Update Database option has been run on your database. You can do this by selecting Utilities-Database-Update Database and follow the instructions. All users must exit completely from our system before running this utility. Please contact technical support at 800-672-9462 x101 if you continue to have problems after updating your database. I updated my PFW/PFD Item Descriptions but the changes are
not being displayed in the comment field of BOM Maitenance. How do I update
the "Comment" field in Bill of Material Maitenance? When pulling in a component in Bill of Material Maitenance the program will copy the PFW/PFD Item Description into the Comment field by default; however, this is just a copy of the item description and is not reading the field directly from PFW/PFD. If you change the PFW/PFD Item Description in PFW/PFD Inventory the comment field will not be updated automatically. This is imperative to many of our users as they make changes, and add information to this field. If the field was updated automatically the updates would be deleted. In Version 3.23 and higher a Comment Utility is included that will copy the PFW/PFD inventory description to the components comment field. This utility will update every component item comment in all bill of materials. To execute the program, find the Maynard Software program installation directory using Windows Explorer and double click on the COMUTIL.EXE. Why is Transaction Posting freezing my system? Are you posting transactions that include serial or lot numbers? The posting program would hang if there was enough lot numbers in two locations but not enough in the posting location. This only happened when interfacing with PFW/PFD version 4.7. This error was caused by a bug in the system and was fixed in version 3.23. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Are you posting Undo Transactions? The posting screen would freeze a workstation if an undo with a serial number was processed. This error was caused by a bug in the system and was fixed in version 4.0. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. I have followed the manual to add options to the
Production Work Order and Explosion Report, but they are not printing. The additional options were not working in the Production work order or the Explosion report. This error was caused by a bug in the system and was fixed in version 3.3. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Why is the serial number field not allowing a full 30
characters? We extended the serial number field to allow serial numbers with length of 30 in version 3.3. To implement this change you will need to install version 3.3 then run the update database utility. You will be prompted "Database is already up to date. Continue with update?" You should respond "YES" to this question and the serial number field will be expanded. Why I am receiving an Error 3134 when using the WIP Commit
transaction? This error was caused by a bug in the system and was fixed in version 3.3. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. When scrolling down the components in Bill of Material
Maintenance the component information at the bottom of the screen is not
always correct. How do I refresh the information? This error was caused by a bug in the system and was fixed in version 4.0. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. When scrolling down the components in the Transaction
Entry Detail screen the component information at the bottom of the screen is
not always correct. How do I refresh the information? This error was caused by a bug in the system and was fixed in version 4.0. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Why are posted transactions causing my PFW/PFD cost layers
to go negative? This error was caused by a bug in the system and was fixed in version 4.0. You should contact our main office at 435-563-1840 for information on receiving the latest version of our software. Revised: 8/20/06 |