As the comments say, create the table with a CSV storage backing and then delete the file and symlink any file to the same location. You are now querying your quicken export or your excel file.
On windows, Logparser 2.2 is a fast implementation of a similar idea.
Does Q handle typical aggravated CSV symptoms such as commas in speechmark delimited strings, speechmarks in speechmark delimited strings, strings that contain carriage returns, etc?
Here's a sample how this can be done: http://fdik.org/ado.zip
Such database middleware is missing on many other platforms. Could be an option to think about it.