Hi David, I've seen this message too recently - in my testing of the variable size scrolling regions.
Unfortunately, I don't know what made it go away but it has. I have to conclude that it is not a bug but, probably, some sort of timing/sequence problem in the code. I was playing with lots of property commands and, because I don't fully understand them all <g>, probably just tried to do something stupid that got corrected with my knowing it. I know that doesn't help much but, hopefully, it gives you something to look for. Regards, Alastair. ----- Original Message ----- From: "David M. Blocker" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Monday, March 28, 2005 7:55 PM Subject: [RBG7-L] - Odd Error Message in form with Radio Button "on click eep" and SPEEDButton > I have a form with: > > A Variable Radio Button with 4 choices > 3 Enhanced Group boxes, each with a label and variable edit in it > 2 Speed buttons (one "search" and one "cancel") > > I'm trying to track down a problem with the EEP from the "Search" button: I > get no error messages, even with SET MESSAGES and SET ERROR MESSAGES ON, but > certain error traps stop working the second time around in the program. > > So, I'm trying to trace, and here's where the wierd message comes in. The > Variable Radio Button has on ON CLICK eep which, based on the radio button > pressed, makes one of the group boxes and corresponding text / variable > visible and the other 2 not visible. This sequence of steps leads to this > bizarre error message: > > 1. Click on one of the radio buttons: first time, works fine, the right > group box comes up > 2. Immediately click again on a different radio button. The eep starts to > fire. When the first line is highlighted (just a SET VAR command) and I hit > F10: I get this message: > > ”Cannot make a visible window modal” > > > > The result is that the EEP doesn't work: I can F10 the rest of the way > through, but the value of the Variable has not changed, the radio button > still shows the first button selected, and the PROPERTY commands did not > work. > > > > The really strange thing is when RUNNING the code, the radio button works > fine and I don't get this error. > > > > Any ideas? With trace getting stuck here I can't check out why the OTHER > problem is occurring. > > > > David Blocker > [EMAIL PROTECTED] > 781-784-1919 > Fax: 781-784-1860 > Cell: 339-206-0261 >
