--
[In HMG] I experienced a similar problem. A main window on start called a procedure that in turn opened a variable number of other windows. If in one of these windows a control was defined that referred to the next control (in the program source), it failed, aka the subsequent control was not recognized. If the second control was placed before the offending control, it worked. In my case I had to change the program logic. I was not able to fix the problem: it seems that defining new windows from a procedure called on main window's init procedure does not work properly.
I don't know if the problem is related with yours, anyway: maybe there is a problem with DisableUpdate... HTH
Dan
--
You received this message because you are subscribed to the Google
Groups "Harbour Users" group.
Unsubscribe: harbour-user...@googlegroups.com
Web: http://groups.google.com/group/harbour-users
---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/harbour-users/74942ed4-1250-4b9d-b4b9-5f6a01c85cafn%40googlegroups.com.