Dynamic View Object Creation and Scope Question

Question

I'm trying to come up with a way to load up an SQL statement into a view object, execute it, process the results, then keep looping, populating the view object with a new statement, etc. I also need to handle any bad SQL statement and just keep going. I'm running into a problem that is split between the way java scopes objects and the available methods of a view object. Here's some psuedo code:
while (more queries)
ViewObject myView = am.createViewObjectFromQueryStmt("myView",query); //fails if previous query was bad
myView.executeQuery();
Row myRow = myView.first();
int rc = myView.getRowCount();
int x = 1;
myView.first();
outStr = "";
int cc = 0;
while (x <= rc) //get query output
Object[] result = myRow.getAttributeValues();
while (cc < result.length)
outStr = outStr+result[cc].toString();
cc = cc+1;
x = x+1;
myView.remove();
catch (Exception sql)
sql.printStackTrace(); myView.remove(); //won't compile, out of scope
finally
myView.remove(); //won't compile, out of scope
//do something with query output
Basically, if the queries are all perfect, everything works fine, but if a query fails, I can't execute a myView.remove in an exception handler. Nor can I clean it up in a finally block. The only other way I can think of to handle this would be to re-use the same view object and just change the SQL being passed to it, but there's no methods to set the SQL directly on the view object, only at creation time as a method call from the application module.
Can anyone offer any suggestions as to how to deal with this?

Answer 1

I figured this out. You can pass a null name to the createViewObjectFromQueryStmt method, which apparently creates a unqiue name for you. I got around my variable scoping issue by re-thinking my loop logic.