BUG: READ DEACTIVATE Runs When BROWSE Called From VALID of GET (129229)
The information in this article applies to:
- Microsoft Visual FoxPro for Windows 3.0
- Microsoft Visual FoxPro for Windows 3.0b
- Microsoft Visual FoxPro for Windows 5.0
- Microsoft Visual FoxPro for Windows 5.0a
- Microsoft Visual FoxPro for Windows 6.0
This article was previously published under Q129229 SYMPTOMS
In a READ with a DEACTIVATE clause, calling a BROWSE from the VALID clause
of a GET triggers the READ DEACTIVATE clause.
CAUSE
As the active window changes, the READ DEACTIVATE is executed. In FoxPro
version 2.x, the READ DEACTIVATE is not called when the BROWSE is executed
from the VALID clause of the GET.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article.
RESOLUTION
An alternative is to modify your code to use a Form and a Grid instead of
the BROWSE command. The Grid object is part of the form and interacts with
all of the objects in a form. Another option is to code a special case in
the READ DEACTIVATE clause. For example, you could set a flag when the
BROWSE is first activated. In the READ DEACTIVATE, verify the value of the
variable, and if the BROWSE has been called, RETURN .F. from the READ
DEACTIVATE. The following sample code illustrates this method:
*Declare a variable that will control whether the READ DEACTIVATE
* returns .T.
cDeactBrow=.f.
CREATE TABLE test (one c(6) , two C(20))
APPEND BLANK
DEFINE WINDOW wintest FROM 1,1 TO 20,20 FLOAT GROW ZOOM
ACTIVATE WINDOW wintest
@ 1,1 GET nvar DEFAULT 1 PICTURE "@*N Show Browse" VALID browser()
READ CYCLE MODAL ;
DEACTIVATE readdeact()
CLEAR WINDOWS
PROCEDURE browser
cDeactBrow=.f.
BROWSE NORMAL
PROCEDURE readdeact
WAIT WINDOW "READ DEACT Shouldn't be called"
IF cDeactBrow=.F. &&Case where you are in the VALID clause of the GET
RETURN .F.
cDeactBrow=.T. && Reset the variable
ELSE
RETURN .T.
ENDIF
MORE INFORMATION
This illustrates a behavioral difference between FoxPro versions 2.x and
Visual FoxPro version 3.0 for Windows. Because the BROWSE window is
different from the READ window, the behavior exhibited in Visual FoxPro for
Windows seems more logical.
For more information about differences between FoxPro 2.x and Visual FoxPro
version 3.0, search for "Differences Between FoxPro 2.6 and Visual FoxPro"
using the FoxPro Help menu.
| Modification Type: | Major | Last Reviewed: | 5/6/2003 |
|---|
| Keywords: | kbBug kbcode KB129229 |
|---|
|