I use EVIEWS 10+
SQL query code can become very long when retrieving data from an odbc source through the wfopen(type-odbc) or the respective import command and selecting the data in an SQL query.
Is there a way to "outsource" the SQL query commands in a separate file when opening/importing data from a ODBC source, and to call them from there?
Code: Select all
wfopen(type=odbc, link) DSN=MYDSN; MYQUERY.SQL @freq U 1 @smpl @all
where MYDSN refers to a system DSN, and MYQUERY.SQL could be an ascii-file containing the SQL-query.
I know that the approach above does not work. It creates the error message
Table 'MYQUERY.SQL' does not exist in WFOPEN(...
But is there another approach to achieve this?