Hi Stephen,
It seems that your problematic script routine name coincides with the name of a VBScript class defined in the routine. We are aware of this behavior.
TestComplete 7 did not check that and this could cause ambiguity in some situations, so TestComplete 8 now checks this. The error message prevents problems which are hard to diagnose, e.g. when you type the problematic script routine name and it is not clear what the identifier means, since this name can be both a script unit name and a class name. We will make the error message more clear in one of future releases. In the meantime, we recommend that you rename the problematic units and change the corresponding USEUNIT statements (you can use the Find and Replace feature to do this).