Thanks for the last post. I've extended the logging and noticed, that something have messed up the dataset's navigation:
Calling: 01.30 | level=1
-Processing: 01.30
--beforenext: 01.30
Calling: 01.29 | level=2
OnCalcField event recall handled, returning: 01.29
--afternext: 01.29
--afterprior: 01.29
Returning: 01.29
Calling: 01.28 | level=1
-Processing: 01.28
--beforenext: 01.28
--afternext: 01.28
--afterprior: 01.28
Returning: 01.28
Calling: 01.27 | level=1
-Processing: 01.27
--beforenext: 01.27
--afternext: 01.27
--afterprior: 01.27
Returning: 01.27
Calling: 01.26 | level=1
-Processing: 01.26
--beforenext: 01.26
--afternext: 01.26
--afterprior: 01.26
Returning: 01.26
Calling: 01.06 | level=1
-Processing: 01.06
--beforenext: 01.06
--afternext: 01.06
--afterprior: 01.06
Returning: 01.06
Calling: 01.07 | level=1
-Processing: 01.07
--beforenext: 01.07
--afternext: 01.07
--afterprior: 01.07
Returning: 01.07
Calling: 01.08 | level=1
-Processing: 01.08
--beforenext: 01.08
--afternext: 01.08
--afterprior: 01.08
Returning: 01.08
!Error at DS position = 01.25: Az argumentumok nem megfelelő típusúak, az érvényes tartományon kívül esnek vagy ellentmondásosak
(Well, the numbers are not in order, I've used the 1st database I've found, and the last error's translation is the same that you get by setting the filter to 0=1. )
It's so easy, and I would have never tought, that my code doesn't work, because one of it's command doesn't work. Now I really have enough from this.
I'll send the data back to the server, and rerequest it with aother querry every time when I show a field on a visual control... I'm still not proud of it, but at least now I know why I have to.
Last edited by MoZo1 : May 13th, 2008 at 6:21 am.
