Remapping Issues. Inconsistencies.

OK, so, there may be a couple of problems.

Problem 1 may be a timing issue where the objects might not be present on screen or recognized before TestComplete times out.  Using extended find as you are doing, while it's really a VERY useful feature, does slow down object recognition.  So, during test run, TC might not have enough time to find the object.  You can resolve this by increasing the Auto-wait Timeout setting under Tools -> Current Project Settings -> Playback

Problem 2 might be the following:

The object identification problems MIGHT not be with the text field itself but with the parent objects that I have indicated (or others that aren't visible on screen).  formCCv3, if any of it's properties changed might be the culprit... or that footer one... or something else.

Brief intro to nameMapping engine... to identify an object, it starts at the root of NameMapping.Sys.  So, if you have something like

NameMapping.Sys.browser.myPage.footer.frame.textbox

if you are trying to use textbox, TestComplete does the following:

1) Check child objects of Sys to see if there is a browser

2) If there is a browser, check child objects of browser for any page that matches the property settings of myPage

3) If myPage is found, check child objects of myPage to for any object that matches the property settings of foot

4) if footer is found, check child objects of footer for any object that matches the property settings of frame

5) if frame is found, check child objects of frame for any object that matches the property settings of textbox

6) if textbox is found, perform the indicated operation

If at any step Testcomplete fails to find what it's looking for, it will fail the whole operation and you'll get an "object not found" error of some sort.

So, in your situation, if any of those parent objects are changing, that could "break" your textboxes.  The solution is to examine those objects and see if there are properties that you can apply to them that won't break as easily.