Karthic,
Hi. Yes in general there are a few features within the module, that when combined, will over-ride the other option. For example if you had both session and querystring enabled then I think session would override querystring etc... It would be nice if we added features in the future that allowed you to choose the 'order' in which would take precedence but this isn't currently a feature.
For now, I would implement something that we have done in the past when we have worked on similar implementations.
A few options...
1. Use another Session Variable that set it blank initially, after page 1 set the value to something else.Then on page 2 set a value to this, such as "DBUpdate" for that session variable.
2. Set your SQL Binding to run two stored procedures based on the session variable, if its blank run the first stored procedure, if its not blank then run the 2nd stored procedure.
There are other ways of doing this but basically you have to run two queries, one for when you want to pull that data in and one for when you don't want to.
Another option: Skip the 'global' SQL Bind and choose to use the 'individual SQL Bind'. Then you can run the SQL Bind on individual fields and possibly have two fields to represent one that you want when the session variable is blank and another when its not using question events.
If you need us to directly help you or assist in your implementation we also offer Premium Support for these types of cases. You can find our more details and/or pick up hours at
http://www.datasprings.com/Premium-Support. Thanks!
-Chad