07-31-2011, 02:41 PM
Thanks, that will be apprecciated 
But I'm seeing that the problem is if the loop at 350. When it finished to print the screen, the code freeze... still searching the cause.
Cheers
EDIT: vars, vars, vars... all the vars need the EXACT kind of var it will be. Also, I've found that mark a var as uInteger and make it through the last number (65535) in a FOT statement, it bakcs again to be 1! So, the FOR statament never ends because when it reach its last value, it goes back again to 1 before the NEXT instruction. Maybe I'm missing something? :?
But I'm seeing that the problem is if the loop at 350. When it finished to print the screen, the code freeze... still searching the cause.Cheers
EDIT: vars, vars, vars... all the vars need the EXACT kind of var it will be. Also, I've found that mark a var as uInteger and make it through the last number (65535) in a FOT statement, it bakcs again to be 1! So, the FOR statament never ends because when it reach its last value, it goes back again to 1 before the NEXT instruction. Maybe I'm missing something? :?