Report Engine getSQLContainer() intermittently fail when trying to pull SQL

Question

Hi,
I am using the following code to open up and extract SQL statements from my webI reports.  The code works fine for nearly all our reports, but for some reports the sqlDataProvider.getSQLContainer() line does not pull the SQLContainer, which results in NullPointerExceptions when I try to do anything further with the container downstream.  I'm wondering what would prevent the SQLContainer from being extracted?  Any ideas?
//get data provider information
DataProviders dataProviders = doc.getDataProviders();
//accomodate multiple data providers
for (dp = 0; dp < dataProviders.getCount(); dp++) {
DataProvider dataProvider = dataProviders.getItem(dp);
SQLDataProvider sqlDataProvider = (SQLDataProvider) dataProvider;
SQLContainer sqlContainer = sqlDataProvider.getSQLContainer();
try{ 
SQLSelectStatement reportSelectStatement = (SQLSelectStatement) sqlContainer.getChildAt(0);  //this throws null pointerexcept
String reportSQL = reportSelectStatement.getSQL();
} catch (NullPointerException e ) {
//catch the exception
Edited by: Jeremy Sartori on Aug 12, 2010 8:50 AM

Answer 1

I don't know if Jeremy got his issue resolved or not, but the following change (see commented out line) to my setContexts caller seems to work:
    private void FillContexts()
        if (_documentInstance.getMustFillContexts())
            Contexts contexts = this._documentInstance.getContextPrompts();
            for (int i = 0; i < contexts.getCount(); i++)
                Context context = contexts.getItem(i);
                String[] allValues = context.getAllValues();
                String[] shortestContext = GetShortestContext(allValues);
                context.enterValues(shortestContext);
           // _query.resetContexts(false);       /*  COMMENTING THIS OUT SEEMS TO FIX XI 3.1 SP3 NULL getSQLContainer ISSUE  */
            this._documentInstance.setContexts();
But I don't want users to be prompted for contexts in generated reports, which is why (I think) the resetContexts call was put in there in the first place.  Is there a better place to call resetContexts(false) that won't have unwanted side effects?
Thanks, Eric