Part Description
 LDR101980 - Cover-camshaft carrier
Supersessions
 
FromItemId
from part
ToItemId
to part
Quantity
Comment
Comment2
Group
Sequence
 
  1992 LDR101980 1814 LDR103250 1   F 1 1
  1992 LDR101980 1843 LLH102380 1   F 1 2
  1992 LDR101980 1845 LLH102390 1   F 1 3
Comments
Change Points
 
FromYear
FromPrefix
FromSN
ToYear
ToPrefix
ToSN
Type
Plant
ComponentId
Related
Component
Max record
id number
ID#
 
        14K4FK76 587389 Engine   57182 57182 24525
        14K4FK77 579905 Engine   57182 57182 24526
Show fields from Show fields from Show fields from a related table
Report Name *
Description
Reports and Charts Panel
Each table has a panel listing its reports and charts, organized in groups.
Please wait while your new report is saved...
Field label
Column heading override
Justification
What does auto mean?
Fields in:

Fields to Extract:

Name for the new table:
Items in the new table are called:

When you bring additional fields into a conversion, Quickbase often finds inconsistencies. For example, say you're converting your Companies column into its own table. One company, Acme Corporation, has offices in New York, Dallas and Portland. So, when you add the City column to the conversion, Quickbase finds three different locations for Acme. A single value in the column you're converting can only match one value in any additional field. Quickbase needs you to clean up the extra cities before it can create your new table. To do so, you have one of two choices:

  • If you want to create three separate Acme records (Acme-New York, Acme-Dallas and Acme-Portland) click the Conform link at the top of the column.
  • If the dissimilar entries are mistakes (say Acme only has one office in New York and the other locations are data-entry errors) go back into your table and correct the inconsistenciesin this case, changing all locations to New York. Then try the conversion again.

Read more about converting a column into a table.