Changing x.dbSQL and Reloading Page

After displaying a grid and/or update form built setting x.dbSQL to a SELECT ...WHERE, I want to reload the same page (in grid mode), modifing the original sql WHERE. I've got it working except that if the user has previously used an "update" form, the ASPdb-Pro page reloads in 'update' mode.

I've forced ASPdb-Pro back to a "grid" on the reload by including request parameters "aspDBBut_4=aspDBgridReload&aspDBClick_4=reloa d".

I noticed that the "real" reload also includes a "Reload=nn" where nn varies from page to page. Am I asking for trouble or should this technique work?

Is changing the dbSQL between iterations of the same page dangerous?

Any ideas or comments would be appreciated!

Hi Abner,

There's a dbReset property that is designed to handle situations like this,
where you're changing properties and want ASP-db to "re-read" everything and
assume it's starting from scratch. Check it out in the online docs at
www.aspdb.com.

Take care,
John


On 2/11/99 1:49:37 PM, Abner Kestler wrote:
> After displaying a grid and/or update form built setting x.dbSQL to a
> SELECT ...WHERE, I want to reload the same page (in grid mode), modifing
> the original sql WHERE. I've got it working except that if the user
> has previously used an "update" form, the ASPdb-Pro page reloads in
> 'update' mode.

I've forced ASPdb-Pro back to a
> "grid" on the reload by including request parameters
> "aspDBBut_4=aspDBgridReload&aspDBClick_4=reloa d".

I noticed that
> the "real" reload also includes a "Reload=nn" where nn
> varies from page to page. Am I asking for trouble or should this technique
> work?

Is changing the dbSQL between iterations of the same page
> dangerous?

Any ideas or comments would be appreciated!