Hi,
Easiest stuff first:
> it's displaying everything disable
Object does not exist (.Exists property equals to False). Thus all other properties are not accessible because they do not exist either.
Now more complex things related to the terminology:
> How can i call my objects
No way. Point.
Objects can not be called. Object is a wrapping structure for the data and methods that process those data. Object must be defined first. I.e. it must be described what data will it contain and what code will process the data. Then the object instance must be instantiated. Instantiation allocates memory to keep data, assigns data to the allocated memory and sets pointers to the processing code. Then you may call the code that will process the data.
Summarizing: object cannot be called, but methods of object instance can be called.
Now your code:
Function AllObjects()
Set abc = ........Something here.......
Set bcd = ........Something here.......
Set cde = ........Something here.......
End Function
The code assigns values (actually - references to some objects) to the abc, bcd and cde variables. As those variables are local to the AllObjects() function, they (variables) are dismissed of on function exit and cannot be used to access the objects that they referenced. (Existence and accessibility of the referenced objects is a separate question and you should read about objects disposal of and memory management in VBScript additionally.)
In order to keep variables and make them accessible outside of the AllObjects() function, those variables must be declared as public. I.e.:
Public abc
Public bcd
Public cde
Function AllObjects()
Set abc = ........Something here.......
Set bcd = ........Something here.......
Set cde = ........Something here.......
End Function
After that in another unit you will be able to do something like this:
'USEUNIT A
Sub TestCase()
Call AllObjects()
Call abc.<SomeMethodProvidedByObjectReferencedBy_abc_Variable>()
End Sub
Note, however, that this approach should not be used in real life for the most of objects of your tested application.
Two primary cases:
a) Global variables are risky because they are accessible from everywhere and may be occasionally assigned some other value in an absolutely different part of your test code and you will have a hard debugging time to resolve this;
b) Objects of the tested application are usually created and destroyed while the application functions. So it is not possible to store the reference to some tested object until this object is created. And the stored reference will be invalidated when the tested object is destroyed in the tested application.
For example: it is not possible to store the reference to the Order Form to the abc variable until the form is opened in the tested application. And when the form is closed, abc variable will reference invalid object that cannot be used. (There are a couple of additional details here but they are out of scope at the moment.)
So, the best approach with TestComplete is to either use the provided NameMapping with Aliases, or to have a set of functions that will search for the required object and return a reference to it (if it exists), but not to try to search for all objects of the tested application on test start and keep references in public variables. This just will not work.
