Here's why: I'd like to create a simple "generic" VB script function to run a SQL command on a "3rd Party" SQL-Server. In my installation program, I'd like to call the CA several times, using different SQL-Scripts, servers, DBs, etc. I'd like to use the path to a SQL Command file as a parameter, then have the VBScript open the file, read it into a string var, and execute it against a SQL-Server.
The SQL scripts are rather large (creating tables, stored procedures, etc.), hence my aversion to coding them directly in the VBScript. If I could open the files in the InstallScript and pass in the entire script text using Session.Property() in the VBScript, that would work too.
The thing I don't know how to do is open an external file and read the text when the file is included as part of the install.