The table could be inserted into the programmation in a different way. In my script (also scripted mainly by someone else), the 'call' function is sometimes used to create a table.With this function, you do manipulate data, but you don't see it in your script. This is because the actual script for the call is found elsewhere.
CALL ScanFolderTrain ('$(vFolderSourceData)\TXT\');
sub ScanFolderTrain( Root)
for each FileExtension in 'txt'
for each FoundFile in filelist( Root & '*nmbsoutput_*.' & FileExtension)
Hour as Hour,
FROM [$(FoundFile)] (txt)
// WHERE TrackNr >0;
//DROP Field Day, Hour;
And the ScanFolderTrain is a .QVS file that sits in a library folder.
In this example, the table Filelist is made.
In my script, the command is followed by a rename command for the filelist table, and that is how I can trace back. In yours, this may not be done, but the table may reside in memory untill used.
Hope this helps...