> Whaat? the monitor shows you the SQL that is being passed from the client
> to the server AND it shows you the parameters. Make sure you always

scroll

> right down the monitor's display, otherwise you will miss most of the fun.

:-)


OK, what I meant is that it shows me all that but all I can see is that that
the parameter is lost somewhere between clicking the header and preparing
the new statement.

>
> This is why the change event of the datetimepicker is the wrong place to
> apply the new value to the parameter.
>

Here I only reapply when the user selects a new date

In order to exclude problems with a too complex dataset I tried to reproduce
the problem using a new DB and a table with nothing more than an ID, a
VarChar, an Integer and a Date. What I found out is that the parameter is
NOT lost upon reordering as long as the WHERE clause is anything BUT a date.
Right now I am testing some more, when I find anything I'll let you know.

> Please don't send support questions to my private email address.

Sorry, wrong button, didn't happen on purpose.

Florian