Forum Discussion

AaronFager's avatar
AaronFager
New Contributor
11 years ago

Creating a new project but using old scripts.

I have code that we have been using since TC3, but we recently rewrote it based on some coding standards.  418 functions in five files are now in 418 files.  I tried to run these though, and I get multiple issues.



Importing the files into the project, I get an infinite "not enough memory error" after it adds about 10 of the functions.  I had to close the process  in order to get out of the loop. 



I figured out that I needed to add them 9 at a time, and then close their windows.  Can I suggest that you not open the code if the set of files being imported is more than 5?



But then I went to run them, and I get the error message "Object doesn't support this property or method"  when it tries to access the first function.  I have the \\USEUNIT in place, and have used it before with no issues.  I moved the first function into the same file, and it gets past that line with no problem.  But then, I get the following message




"'Files' is undefined".  So, it seems to me that creating a new project is treating me like a novice.



Please note, the code is the same as what we are currently running, we are just movig it to a new project with different standards.  But in this new project, the script files have a white arrow pointing SouthEast on top of the script icon, and apparently cannot see each other, even though the syntax check is successful and it does run when I have all the functions in one file.



Is there some basic step I am failing at?  Please note that I used to help out in the old Automated QA forums and know much of the basics, but it seems that the jump from 4 to 9 has me stumped.



Thanks in advance,



Aaron.





 

  • AaronFager's avatar
    AaronFager
    New Contributor
    Forwarded the issue to support.



    However, just mentioning that the part about a blue box with an arrow seems to be when the script files are outside of the parent project.  A previous question led to the suggestion that all the files get copied into the new project's script directory.



    That removed the blue boxes, but the issue remains.