The script from the original file is not accessible from the script you put the binary load in.
If you can open the original file, just copy the field names as necessary to the new file.
If you can't open the file / access the script, you can look at the table viewer (CTRL-T) or use the system table to have a look at the fields used.
I think you would need to do a resident load if you want to transform some fields.
The binary load does only load tables and fiels (and values, of course). But once you have binary loaded a file, you can get to the Table Viewer, or use two listboxes with system fields $Table and $Field where all tables and all fields are listed.
Of course, you can do RENAME, DROP, LOAD ... RESIDENT from the tables already existing, although you cannot change the original script, because it is on a different file.
Hope that helps.
After a binary load the data model is (as you have seen) intact, and the script is effectively as it is at the end of the script running in the QVW you have done a binary load from.
This means that you can issue statements like DROP TABLE and DROP FIELD to remove items from the data model. If you wish to rename fields you will need to do a RESIDENT load and use the AS statement to do the rename.
Given the main advantage of a Binary Load is its speed and that Resident loads are inherently reasonably slow - you might want to steer clear of renaming of fields in this way - and perhaps rename any fields in the QVW you are loading from?
Hope that helps,
You can't modify the script as such. A binary load doesn't get the script from the other QVW but gets the already loaded datamodel. What you can do though is modify the datamodel. You can perform resident loads of tables in the model, join to tables in the model, drop tables and/or fields from it, etc etc