What you need to do is edit the item that is mapped as Aliases["FarmaPro"]["FarmaProForm"] to apply either new criteria (if they have changed) or modify the existing criteria to be more resistant to changes. The articles posted in this thread should give instruction in how to do so.
Two things cause a component to change identification.
1) The application itself has changed fundamentally to require remapping
2) The component has certain dynamic properties (ID, name, etc) that need to be accounted for in the mapping. I suspect that this is the case with your situation. You'll need to either use a different set of criteria to be able to uniquely identify FarmaProForm so that it does not have to be changed frequently, or you'll need to modify your existing criteria (with wildcards, conditional mode, required children, etc), to make it more flexible.
A good video tutorial on this can be found at
http://smartbear.com/support/screencasts/testcomplete/reliable-tests-for-dynamic-objects/Without knowing the specifics of your component, what properties are being used, which properties have changed, etc, I cannot be any more detailed.
If you can post a screenshot of the Object Spy for the form in question and a screen shot of the mapping criteria for FarmaProForm, I can give some advice but, right now, all I or anyone can do is generalize.
