Hi!

Its much the same as I suggested about "parts" of the form. Try to locate the exact thing that causes problem. With such a complex form you require a regular, strict approach like I described. Otherwise this will going to look like a catching of the bug running somewhere underground of the large field.

As about the kiddie code, I guess it is a good reson to say that you require to learn more about OOP and good programming code writing. This will eliminate 90% of such weird errors in VFP application. Just good discipline in codeing and standards is the best preventive thing.

HTH.

>Well, just set step on in the top of refresh method and execute it line by line to see, what's the problem. It might be related with checkboxes behavior.
>
>If you think it's related with navigation button class, trace it down from there...
>
>>Nadya, Don't take this personal, this "refresh" problem is getting to me
>>it really seems to be conntect to the navigation button class
>>
>>everything in the refresh is needed because of the navigation buttons and the nature of the form with graphical checkboxes, calling extra methods will slow the program down just as much, also I think that is the shortest refresh method I have in my "complex forms"
>>
>>unefficiencies, unefficiencies. well thats kinda why I said "kiddie code"
>>
>>unefficiencies is not the issue or the problem, if you like nit pick something I all ready said wasn't golden, then do so to yourself, I am worrying about programmatic errors, beautifying code is the last thing I am worrying about
>>
>>I do a lot of my coding styles so it is easier for me to spot errors, once I am sure that everything runs smooth, then I go back and simplify the code for efficiency
>>
>>everytime you try and respond to a problem I am having you go off on tangents on unrelated issues, I do greatly appreciate all input but could you stick with the topic??
>>
>>
>>>Stephen,
>>>
>>>My advise to you would be re-think your logic. Are you sure, you want to put all this complicated logic in Refresh method of the form? It seems to be not efficient. It's much better, in my opinion, to put such logic in Form's custom method and call it only when it's needed. I didn't try to analyze the code, though bunch of unefficiencies caught my yes immediatelly. For instance, you don't have to run replace statement multiple times if you can do one replace command. It should be quickier, though the difference might be unnoticable.
>>>
>>>Anyway, look though the code carefully, make adjustments, when see, if you can reproduce the problem.
>>>
>>>Finally, checkboxes have some funny behavior too. Check quite recent posts from Barbara Paltiel about this problem...
>>>
>>>>No done that didn't help a bit
>>>>