4D Components are useful ways to move and apply a group of methods and functions between 4D databases. While they can be easy to neglect when it is easy to copy and move the component over, it is important to make sure that the version of 4D and the target processor that the component was compiled for matches that of the host database.
If these items do not match there can be various outcomes:

• The component appears to work properly
• The compnent does not work properly
• The component does not load

With the variance of the potential outcomes it is suggested to make to to use the proper version of a component.