General information
Category:
Forms & Form designer
Environment versions
Network:
Windows 2003 Server
Or Freud -- "Sometimes a cigar is just a cigar."
>Actually, I think the original came from Groucho Marx "Close, but no cigar"
>
>>Is that anything like the Soup Nazi on "Seinfeld"? ;-) "No cigar for you!"
>>
>>>Close, but no cigar for me!
>>>
>>>thanks Naomi
>>>
>>>
>>>>The setting is SET NOTIFY.
>>>>
>>>>Set SET NOTIFY OFF to not show this wait window.
>>>>
>>>>>My guess would be you have TALK turned OFF in the first, and it's set ON in this one
>>>>>
>>>>>
>>>>>>I have a form (more than one, I'm sure) where a textbox is used to enter a value, the system looks up the value in a table, and populates a grid with some information from the record that is located. If data was entered, I return false so that the user can continue to enter values. If no data was entered, I return true so that the user can exit the control. This is done via the Valid method. It works like a champ. Now I am developing another form where I am using that same technique and, although it works, I get a beep and an "Invalid input" wait window when I return false. Actually, I believe this latter behavior is the std. behavior. The odd thing is that I don't know why I'm not getting it on the first form. I'd like to get rid of that behavior and have it work like the first form. I don't have anything in my base class that would affect this. Does anyone know why I might be getting the different behaviors?
>>>>>>
>>>>>>Thanks,
>>>>>>
>>>>>>Russell Campbell
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only