|
An item in an Xfmea Standard or RCM++
database (MS Access) is corrupted and the following message displays: "The FMEA for this
Item has become corrupted and the Item should be deleted."
Issue
Discussion:
ReliaSoft's
Xfmea Standard and RCM++
software products work with Microsoft Access® databases in the back end for storing
analysis data. These database and library files (*.rx4 and *.lb4) will be subject to the same
limitations and vulnerabilities as any other Access® database. As described in the Microsoft
publication at
http://support.microsoft.com/kb/283849/EN-US/, "it is not possible to reliably prevent
any and all database corruption." Database corruption may be the result of factors outside
of the control of the Xfmea/RCM++ software, such as faulty network hardware, an
unexpected "crash" of your PC or a network interruption.
If the
analysis for one particular item in your Xfmea Standard or RCM++ database becomes corrupted, you
will receive the message "The FMEA for this Item has become corrupted and the Item should
be deleted. If desired, you can export the Item's FMEA to Excel, create a replacement Item and
then re-import the non-corrupted FMEA data" when you try to open it.
For information on what to do if your entire database is corrupted, please
read Technical Support document # 20012.
Solution:
In Xfmea Standard and RCM++ you can use two methods to salvage the corrupted data items:
- You can export the affected data to Microsoft Excel, then re-import the data by doing
the following:
- Select the item in the System Hierarchy panel.
- Select Import/Export Item’s FMEA and then Export to Excel from
the System Hierarchy menu.
- Create a new item in your project.
- Select Import/Export Item’s FMEA and then Import from Excel from the
System Hierarchy menu to re-import the data from Excel to the new item.
- Finally, delete the old, corrupted item.
or:
- Create a new item. Use the Copy Multiple FMEA Tree Items command
from the Edit menu to copy all functions from the old, corrupted, item and then
paste the functions to the new item. Finally, delete the old, corrupted item.
Technical Support document # 400010, presents some recommendations
for standard precautions that users can take to protect against corruption and reduce the impact
of the data loss if corruption is unavoidable.
Please contact ReliaSoft's Technical Support via
phone, fax or e-mail and provide as much information as possible about exactly what you were doing when
the corruption occurred. Whenever possible, please provide a copy of the corrupted file. In some
cases, ReliaSoft may be able to provide assistance with salvaging some or all of the affected
data. However, in many cases, the best recourse may be to restore the latest backup from before
the corruption occurred.
Related
Records:
RS 400010
RS 20012
|
